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? > # Desirable Trac Features # > > * more statistics > * a default CC to a google group sage-trac, this requires that a > google group is created [done] and that somebody with admin > access to sagemath.org enables smtp for trac [not done yet] > * loads more interesting bits at http://trac-hacks.org/ - but we > should not merge in too many extensions because it makes > maintainability more difficult once we upgrade to newer trac > releases. I maintain several phpBB installations and not > adding a wild bunch of mods proved to be a smart choice. * Mercurial bundle browsing. I don't know how hard this would be to do, but I might end up doing some trac hacking as part of my TA appointment here so I could perhaps look into this. - Robert --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
