>> And, let's be honest, no >> release cycle is really going to be much shorter than that. > > Are you sure? I personally did 100% of the releases for 3 years with > an average of 1-week for the release cycle. >
Who knows -- maybe I'm wrong? Do you want to test it? Try doing sage-4.2 in a week. Or even two. I don't know -- maybe this will be easy? Maybe it will be impossible? Maybe you can do it, but you won't get anything else done in those two weeks? (My money's on that last one, with it coming in right at two weeks at best.) Is there a table somewhere of Sage versions and release dates? I don't know that I said this explicitly in my last email -- I like our system of shorter release cycles in general. That said, I don't think we need to say "we must have a release every three weeks!" We should say "three months is too long!" All in all, I don't think there's a need to rush -- it should be up to the release manager to say "okay, we've merged a bunch of stuff, and the other big stuff on the horizon is still at least a week or two off -- let's feature-freeze and start cleaning up the current build/doctest failures." In short, I guess I'm saying that I don't think there's anything *wrong* with the system as it currently stands. I think the only weakness is that there aren't enough people who have the time and energy volunteering to be release manager right now. As I mentioned above, I think part of the problem is the time commitment (*especially* for your first release), but maybe not. -cc --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
