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. |
| 5 | For [milestone:unscheduled] tickets, where many "patch welcome" type tickets end up, 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: |
| 6 | * well exposed rationale for the change |
| 7 | * clarity and correctness of the code |
| 8 | * unit tests, functional tests |
| 9 | * etc. |
| 10 | |
| 11 | See TracDev/SubmittingPatches#Whatisagoodpatch for more details. |