Hello, since this has come up repeatedly I would like to clarify: Do not close any tickets in trac unless you have been explicitly told to do so by either malb, was, cwitty or mabshoff. This is to avoid having issues slip through the cracks. Once a ticket is closed and off the top of the time line chances are nobody will ever look at it again unless you stumble across it by accident.
Just like the "[with patch]" byline we should come up with something to indicate that a ticket should be looked at like "[should be closed]", "[is invalid]" or "[is won'tfix]". In addition you should give a reason why you think the action you requested should be taken (the more precise the better) and retag the ticket against the current target, i.e. 2.8.9 at the moment. If you leave it in 2.9 for now it is unlikely to be found and looked at because there are another 140 tickets open against that one. William can configure trac so that closing tickets is limited to a few, but so far he has not done so. But as we have to deal with an ever increasing number of tickets we need to follow the process in order to avoid losing issues and also keep the confusion and the work to deal with tickets to a minimum. Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
