Robert Bradshaw wrote: > On Sep 23, 2007, at 9:00 AM, mabshoff wrote: > >> # Closing Tickets # >> >> * if you have a solution/patch attach it to the ticket and indicate >> that there is a solution available by adding "[with patch]" to the >> title. It might also be a good idea to reassign the ticket to the >> current bugfix release if it is scheduled for some milestone that >> is far in the future. >> * Do not close the ticket, but let William close it once the patch >> has actually been merged. In the past patches have been lost due >> to the fact that somebody closed the ticket and William never saw >> the patch. Another possibility is especially during Bug Days or >> interactive discussions via IRC that you can close it after you >> have been encouraged to do so. > > How hard would it be to make a new status for "fixed" (as opposed to > "committed/released") rather than modifying the title or something > equally hackish? >
How hard would it be to add a few states to track the development of a patch (I'm modeling this after Drupal ticket tracking): "states" of a ticket: active active (needs more info) patch (code needs work) patch (code needs review) patch (code needs to be committed) fixed duplicate invalid worksforme wontfix bydesign where the last 6 states are "resolved" states (and the last two states may mean the same thing, but it sounds nice to say "bydesign" than the flat refusal "wontfix") -Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
