When you say "Any new ticket should be a real blocker" I presume you only actually mean tickets asking for resolution before 3.1.1? I recently created a new ticket which can certainly wait until 3.1.1 (it's not even a bug, but a new feature).
John 2008/7/19 mabshoff <[EMAIL PROTECTED]>: > > Hello folks, > > due to the ssmod and the gfe2 bug in Sage we really want to have a > stable release out by Wednesday when William gives his talk at ISSAC. > Since we don't want to cut it too short that means that I just moved > all but the above two tickets to 3.1.1. Any new ticket should be a > real blocker, i.e. segfault fix, horrendous memory leak or some major > generic embarrassment. > > So the plan in detail: > > 3.0.6: Sunday/Monday with binaries done by Tuesday > > 3.1: Should open right after 3.0.6 and the first patch in should be > Robert's new parent.pyx. To quote Robert from > http://groups.google.com/group/sage-devel/msg/6162d308061333ef > > [quote] > In terms of status, I got the new parent under the old parent (and > all doctests passing) and swapped out the coercion models (in the > process of writing a compatibility layer for old parents). When this > goes in, we can start writing against the new model. QQ, RR, CC, > etc. > will probably be the best examples. > [end quote] > > Then we might or might not merge some other tickets depending on > Robert's wishes/stability. > > 3.1.1: Merge as usual > > 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 -~----------~----~----~----~------~----~------~--~---
