On Sep 26, 2014, at 6:33 AM, kcrisman <kcris...@gmail.com> 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 > > > This is nearly useless, though, except for tickets modified since the last > Sage (official) release. Is there any way to get back to the "old" system > where the milestone would change *without* changing the ticket - and hence > the ticket last-mod time? It is very misleading to see ticket #xyz modified > three weeks ago and it turns out that it was last substantively modified in > 2008.
Do we really need to change the milestone every time? Why can't we just set them all to future, and then when they get merged, we can change the milestone to the actual version? As it is now, it seems milestone serves no real purpose. It's not the version it was originally reported against. It's not the version it's going to be fixed in. It's just the next release that will be made. -Ivan -- 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.
