On Thursday, January 3, 2013 9:52:07 AM UTC-5, Jean-Pierre Flori wrote: > > > > On Thursday, January 3, 2013 3:46:08 PM UTC+1, Charles Bouillaguet wrote: >> >> Hi, >> >> I have found a few tickets that have been magically resolved ; the >> problem at the origin of the ticket (apparently) no longer exists in the >> current version of Sage, yet the tickets are still open (maybe because >> nobody noticed the problems have been > > This happens all the time with upgrades to component software that fixes various issues/tickets that the people who do the upgrade in Sage didn't know were there, or had forgotten about. E.g. #5917 is so old that it isn't surprising it has been fixed.
> solved). How do we handle these tickets ? Mark them as invalid/won't >> fix/duplicates ? Give them a positive review ? >> > Maybe also add doctests (with a reference to the tickets) showing that the > problems are actually solved? > >> Absolutely. We want to prevent regression. Another reason to do this is that it's conceivable that the error was actually partly OS-dependent and that was not recognized at the time, so that others testing the patch will see that it still doesn't work. You're right though that some of them are unreasonable or hard to doctest. How do we usually test timing ones? It's pretty machine-dependent, so it might be hard to do properly. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
