5 | | For [milestone:unscheduled] tickets, the requirements are a bit stronger: as no Trac developer has shown interest in making the bug or feature request part of the Trac roadmap, the patch has to be very convincing: well exposed rationale for the change, clarity and correctness of the code, unit tests, etc. See TracDev/SubmittingPatches#Whatisagoodpatch for more. |
| 5 | For [milestone:unscheduled] tickets, the requirements are a bit stronger: as no Trac developer has shown interest in making the bug or feature request part of the Trac roadmap, the patch has to be very convincing: well exposed rationale for the change, clarity and correctness of the code, unit tests, etc. See TracDev/SubmittingPatches#Whatisagoodpatch for more details. |