Hello folks, now that 2.8.13 is out it is time to get the ball rolling on the 2.8.14 release. It is the thanksgiving weekend in the states, so we might experience a little slowdown this time. There are plenty of patches and open issues for 2.8.14, see
http://www.sagetrac.org/sage_trac/query?status=new&status=assigned&status=reopened&milestone=sage-2.8.14 If you submitted a patch or bundle please make sure that it applies cleanly against 2.8.13, otherwise please rebase the patch and update it in trac. Feel free to fix other tickets not yet assigned to 2.8.14, just retag those tickets against 2.8.14 so that I can pick them up easily. I am unsure if everybody knows about the new review requirement, but patches are supposed to be reviewed by somebody else than the original authors. If your patch is unreviewed please ping somebody you think is capable of doing so and familiar with the code in that area. The reviewer should comment on the track ticket. William has suggested that if somebody else wants to help doing a release cycle he/she should speak up now. Unless somebody steps up I will also do this release cycle. There are several tickets against 2.8.14 that should be closed as invalid in my opinion. Those are: #787 (superseded by new code) #1130 (better code in mwrank, also the code seems buggy) #1143 (Paul pointed out that William misunderstood) William, can you do that? alpha0 is planned for some time late Friday/early Saturday, depending on how much trouble there will be it might move around a little. Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
