On Thu, Jun 3, 2010 at 12:07 AM, Florent Hivert <[email protected]> wrote: > Hi William, > >> > 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. > > Hum ! Isn't it a little short to expect feedback from France (Your e-mail > arrived here at 00:02:10 this morning and it's now 08:31:50)... Unfortunately > you bumped away #8881 because I forgot to mention that it depends on #9104. > >> 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? > > I'm sorry to say that but this isn't very realistic and helpful either to > suggest that Nicolas or I could be a release manager while we are struggling > reducing the queue, organizing a sage meeting in two weeks, answering request > for documentation and help on categories on sage-algebra and sage-combinat and > at the same time, closing the academic year in our respective department (Exam > to prepare and grade -- no T.A. for that here -- student which are making > summer experience in private companies to visit, evaluations to > prepare, etc)... I also forgot to add giving two talks (one next Tuesday, one > next Friday) in some research seminar about sage and its use in our research. > > Also, since we are at it, I've no idea how big is the work of a sage release > manager, but I can tell you that keeping the combinat queue in line against > several sage release, testing the patch on it and rebasing it at each release > is a work I feel close (though certainly much lighter) to be the one of a > release manager. Nicolas and I keep doing it without any allowed break. > > I'm sorry for the negative tone of this e-mail but when I said we are > struggling I meant it. By the way, there is a good risk that Nicolas won't be > able to answer his e-mail before this evening. So don't expect more feedback. >
I'm sorry, but sage-4.4.3 is now in feature freeze, since (1) it is already going to be difficult to release as is, (2) nobody is helping me, (3) I don't have much time to work on sage releases right now. Here's how it will go down: a. I will do whatever it takes to release sage-4.4.3. b. I post to sage-release asking for somebody to be release manager for sage-4.4.4. -- William -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
