Hello folks, the time frame to get patches into 3.2.1 is nearing its end with a planned release in 48 hours. Anything going into 3.2.1 at this point should be well debugged and tested and be critical or blockers. Any other tickets should automatically get assigned to the next milestone. This release is about half a week earlier than initially planned since alpha2 seemed much more stable and with fewer problems than anticipated. Since the release cycle of about once a month for the last three months has been too long we have been more aggressive of pushing for quicker releases and want to hit 7 to 10 days for bug fix and about 12 to 18 for major releases. Obviously such a release cycle will vary due to unforeseen issues. After all: This is software development and not engineering :)
Unlike the initial plan from two weeks ago we will shove in an additional stable release, aka 3.2.2, but it should also be on the short side. This is meant to merge patches from trac and also to get as much of the sage-combinat code that is ready in before the big 3.3. ReST conversion. So if you have code sitting around please try to get it polished and into 3.2.2. There will be tools for the ReST transition, so if you miss the merge window before 3.3 it won't be too bad. Thoughts? Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
