We do use the milestone to indicate duplicate/invalid/wontfix, at least.
Though I agree that we don't really need to update the milestone, if its
pointing at an older version then so what? Is anybody making trac queries
for specific milestones? If you want to know which tickets were closed then
On Sep 26, 2014, at 6:33 AM, 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
>
>
> This is nearl
> 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 #xy
On 2014-09-26 14:50, kcrisman wrote:
I wish I could! I recall that Jeroen had to always ask someone else to
change the milestone, even he didn't have access to it as release
manager :)
Nobody ever told me how it was done, but I assume it was indeed a direct
manipulation of the Trac database.
>
> 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 t
On Friday, September 26, 2014 1:33:36 PM UTC+1, kcrisman wrote:
>
> 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
> > 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
On 2014-09-26 12:36, Jori Mantysalo 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
--
You received this message because you are
After clicking Lastmod-header it got tickets sorted like
1 mins < 23 hours < 32 mins < 8 days
Is this bug in trac in general or some setting at sage trac?
--
Jori Mäntysalo
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from th
