> > > All I can see from trac is that everything happened 22 months ago. How > do I > > find how long it took to go from positive review to stable release? > > ... a search of sage-release would show the dates when the > release manager made a particular release. I think times (in days) are > far more useful than actual dates, but you can work out the days from > the dates. > > Unfortunately, we no longer use the "Merged in" part of Trac, which was a VERY efficient way to find this out. Searching through git history and then trying to forward to the next release is something for git wizards, no doubt some command using tag... amazingly, I found something relevant.
$ git tag --contains 4f8b380 6.4.rc1 6.4.rc2 Hope this helps. It should not be necessary for people to spend time figuring this out, though; you should be able to work it out without using Trac or searching through sage-release - indeed, without knowing about "commits" at all, because many people who want to know what version of Sage has such-and-such fixed won't be developers, just users. - kcrisman -- 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.