The trac tickets can pile up, this slows down development and can obscure important bugs. To help the developers a report has been generated showing all tickets which currently haven’t been given a milestone.
If tickets show up on that report, you need to review them & check them for validity.
For Bugs:
If you can reproduce it, set the milestone to 1.0
For Enhancement Requests:
Unless it sounds serious, defer it.
For patches:
Set the [PATCH] in the summary and set the milestone to 1.0.
There are some useful canned responses below.
Can’t Reproduce
Thanks for taking the time to submit this bug report. Unfortunately I’m unable to reproduce this bug based on the information you’ve provided.
$CUSTOM
If you’re still having this problem please attach a simplified version of the code which triggers the bug, and detailed steps to reproduce. Or alternatively the problematic code itself.
Insufficient detail
Thanks for taking the time to submit this bug report. Unfortunately I’m unable to investigate this bug based on the information you’ve provided.
$CUSTOM
If you’re still having this problem please attach a simplified version of the code which triggers the bug, detailed steps to reproduce it and the exact error message you receive.
Enhancement pushed out to 1.x
I’m setting the milestone for this ticket to 1.x; this means that the earliest it will be implemented is after rails 1.0. If you feel this functionality should be included in the 1.0 release please email the developers list to discuss it.
Alternatively you could implement the functionality yourself and add a patch for it, that makes it much more likely to get included.
Defect pushed out to 1.x
I’m setting the milestone for this ticket to 1.x; this means that the earliest it will be fixed is after rails 1.0. If you feel this should be fixed before the 1.0 release please email the developers list to discuss it.
Alternatively you could implement the functionality yourself and add a patch for it, that makes it much more likely to get included.
XPATCH set to 1.x
I’m setting the milestone for this ticket to 1.x, this means that the earliest it will be included is after rails 1.0. If you feel you can complete this patch (including unit tests) in time for 1.0, please feel free to change the milestone back.
[PATCH] added
Thanks for contributing to Rails! In order to get your patch reviewed by the core team, I’ve added [PATCH] to the summary. Next time you attach a patch, make sure you add it yourself. It gets your contributions reviewed much quicker.
Almost Patch
Thanks for taking the time to submit this report, and for tracking down the problem. Would you be able to generate a patch for it? We have instructions available at http://dev.rubyonrails.org/