On Wed, Jun 2, 2010 at 3:02 PM, William Stein <wst...@gmail.com> wrote: > On Wed, Jun 2, 2010 at 1:31 PM, Nicolas M. Thiery > <nicolas.thi...@u-psud.fr> wrote: >> Dear release managers! >> >> What's the current time line for Sage 4.4.3? >> >> We have been working hard those last days on flushing the >> Sage-Combinat queue, and have more than 25 patches with positive >> review ready for inclusion. Well, there is still some work ahead, with >> 15 patches under review and about 125 others still under development :-) >> >> We have a developers meeting on June 14-th - 18-th, and it would be of >> great help if those patches could be merged in 4.4.3 by then, or even >> better if 4.4.3 was released. Any luck? >> >> Thanks! > > Basically nobody has been working on Sage releases lately. I did some > work on 4.4.3 during > the first day of Sage days last week, and it has lingered, because I > simply don't have the time. > There are 94 tickets with positive review: > http://trac.sagemath.org/sage_trac/report/32 > > There is also an alpha1 of sage-4.4.3 here, and two tiny doctests failures > > > http://sage.math.washington.edu/home/wstein/build/release/4.4.3/sage-4.4.3.alpha1.tar > > Failures on sage.math: > > sage -t -long "devel/sage/sage/graphs/generic_graph.py" > sage -t -long "devel/sage/sage/sets/set.py" > Total time for all tests: 8037.9 seconds > > This fails to build on OS X, due to some changes we made to get it to > build on Cygwin. > > The alpha above makes almost no changes to the core Sage library. > > Of the "25 patches with positive review ready for inclusion" that you > mentioned above, > are they all changes to the core Sage library? Or do the patch spkg's, etc.? > > One possibility would be to test/stabilize the current 4.4.3.alpha* > (i.e., fix the fallout from the cygwin > related tickets), include those 25 patches (all to the sage library), > and release 4.4.3 on Saturday. > If you like that, then make a clean sage-4.4.2, apply all 25 patches, > test it, and I can just pull those > changes in, and that will be 4.4.3.
Hi, I didn't get any feedback on this proposal, and now I've decided to just do a feature freeze on 4.4.3, since I applied all the critical/blocker fixes listed on trac, fixed the bugs mentioned before (with sets and pynac), and just want to release something after going through the build checklist. It would make great sense to have another Sage release before June 14. I don't want to be the one to make it. If you really want one that definitely has the combinat stuff correctly merged in, perhaps you could be that release manager, taking the 4.4.3 release as a start? William -- William Stein Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
