On Sat, Feb 20, 2010 at 5:20 AM, Minh Nguyen <nguyenmi...@gmail.com> wrote: > Hi folks, > > On Sat, Feb 20, 2010 at 11:58 PM, slabbe <sla...@gmail.com> wrote: >>> This is the final alpha release of Sage 4.3.3. The next release would >>> be an rc0. The development version of Sage is now in feature freeze. >> >> Does that mean only ticket solving a defect will be merged into sage >> until sage-4.4.1? >> >> The Sage days 20 are beginning on Monday. I think there will be a big >> loads of tickets being created/reviewed/solved in the next 10 days. >> Moreover, I will explain how to contribute to sage to at least three >> persons. It would be nice if their first ticket could be reviewed and >> merged in sage-4.3.3....especially since sage-4.4 is planned to be a >> stabiliser release. If it is fine with release managers, I would >> propose a sage-4.3.3.alpha2 version that would contain the first quick >> results of Sage Days 20. > > I would like to put forward a proposal for creating a Sage > 4.3.3.alpha2 release that would incorporate positively reviewed > tickets resulting from Sage Days 20.
I think it would be much, much better to release 4.3.3 ASAP (say tomorrow!). You, Mitesh, and countless build testers have already put a huge amount of work into stabilizing that release, and it contains many critical bugfixes (e.g., for the notebook) that I wish we had released a week ago. Waiting for patches to be written and refereed, etc., from another Sage Days will simply push the release back at least two weeks. I think we should release 4.3.3 as soon as possible. If there are suddenly a bunch of positively reviewed tickets in http://trac.sagemath.org/sage_trac/report/11, then make a 4.3.4 release in a week. Regarding the stabilization 4.4 release, I see the point of that release to: (1) deal with a bunch of really annoying critical bugs (2) not rush. So I don't see it as absolutely having to be right after 4.3.3. William > There was a recent vote to create > a Sage 4.4 "stabilization release" [1,2]. If implemented, this > stabilization release is to fix (long-standing) annoying bugs, among > other stabilization fixes. I think the Sage-Combinat team also > anticipates that there would be new features and bug fixes resulting > from Sage Days 20, and it would be good to get those merged as soon as > possible. If a Sage 4.3.3.alpha2 is to be created, I expect Sage 4.3.3 > to be out early March. I hope 4.3.3 can be out... tomorrow. > > Thoughts? > > >> Cordially, >> >> Sébastien > > [1] > http://groups.google.com/group/sage-release/browse_thread/thread/185cc40eaff38e1c > > [2] > http://groups.google.com/group/sage-devel/browse_thread/thread/185cc40eaff38e1c > > -- > Regards > Minh Van Nguyen > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To post to this group, send email to sage-rele...@googlegroups.com. > To unsubscribe from this group, send email to > sage-release+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sage-release?hl=en. > > -- William Stein Associate 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
