kcrisman wrote: > > > After clicking Lastmod-header it got tickets sorted like > > > > 1 mins < 23 hours < 32 mins < 8 days > > It's not a direct answer to your question, but you might be interested > in http://trac.sagemath.org/report/92 > <http://trac.sagemath.org/report/92> > > > This is nearly useless, though, except for tickets modified since the > last Sage (official) release.
It depends... The report -- depends on what you expected. (E.g. include *who* modified the ticket.) But it's (been) a continual ping to the people involved in the tickets (including reporter, authors, reviewers), so IMHO useful. They'll get reminded of the ticket and will (hopefully) for example continue working on it, set it to "needs info", or ask for closing it. This has happened hundreds of times in the past IIRC. (William's nagbot is no longer active.) Although the Sage releases are linear (nearly every stable release is based on the last "devel"), for a release manager it makes pretty much sense to change the milestone of tickets (and the default milestone for new tickets), mostly in order to postpone tickets to a later (than the next stable to be released) version. (We for example for a long time had the milestone sage-5.0, which to that time was far future -- goals.) For developers, it makes sense to let them know that their tickets e.g. *won't* get into the next [stable] release, similar to but more explicit than announcing a feature freeze (where? usually not on the tickets where people are cc'ed). -leif -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
