On Friday, October 19, 2012 10:56:46 AM UTC-4, Dima Pasechnik wrote: > > > > On Friday, 19 October 2012 17:32:12 UTC+8, Timo Kluck wrote: >> >> >> Op vrijdag 19 oktober 2012 01:30:07 UTC+2 schreef Dima Pasechnik het >> volgende: >>> >>> On Thursday, 18 October 2012 20:01:51 UTC+8, Jeroen Demeyer wrote: >>>> >>>> On 2012-10-18 11:20, Timo Kluck wrote: >>>> > This ticket [1] adds a %prun directive for profiling to the notebook. >>>> > The release notes for 5.3 [2] say it has been merged, but in fact it >>>> hasn't. >>>> That's a bug in the release notes. Nothing has been merged for #5814. >>>> >>>> at the time of 5.3 release this ticket was closed as invalid. In that >>> sense it was "merged" :-) >>> >> >> I see :-) >> >> Anyway, I just wanted to make sure that whatever happened will not >> interfere with this ticket getting reviewed and merged at some point. It >> sounds like it won't, right? >> > > indeed, changing the status of tickets happens relatively often. > > And this is exactly why I think that tickets involving sagenb should NOT be closed until it is clear that the changes are in upstream or even when that upstream is merged. We don't do this for bugs in Maxima; why would we change the policy for sagenb, if it's truly "upstream"? See for instance the recently opened http://trac.sagemath.org/sage_trac/ticket/13625 - should we close it now that ppurka reported it upstream? Of course not.
In this case, Timo actually made a branch and so forth, but reading the github stuff it seems like there was quite a bit of other action, and even though it "turned out" that the problem was in the Sage library, this easily could have gotten lost. Until things are fixed upstream and we've gotten it into Sage, let's not close tickets saying they are invalid. - kcrisman -- 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.
