| 257 | | 4. If a ticket has an associated patch (see below), a triager will review the |
|---|
| 258 | | patch. If the patch is complete, it'll be marked as "ready for checkin" so |
|---|
| 259 | | that a core developer knows to review and check in the patches. |
|---|
| | 257 | 4. A ticket might be moved to the "Someday/Maybe" state if it's an |
|---|
| | 258 | enhancement request we are willing to consider if a good patch is |
|---|
| | 259 | written. Such tickets are not high priority. |
|---|
| | 260 | |
|---|
| | 261 | 5. If a ticket has an associated patch (see below), a triager will review |
|---|
| | 262 | the patch. If the patch is complete, it'll be marked as "ready for |
|---|
| | 263 | checkin" so that a core developer knows to review and check in the |
|---|
| | 264 | patches. |
|---|