Hello, On Wed, Oct 14, 2009 at 1:21 PM, William Stein <wst...@gmail.com> wrote: > Definition: Release management is the process of taking these tickets, > applying them, bouncing those that don't work, creating a sage-4.2.tar > that works on our supported platforms, and creating binaries. If an > unacceptable number of patches bounce, we delay the release until the > relevant tickets are rebased. > > There are other things that people might do to ensure that sage-4.2 is > a good release, e.g., encourage people to fix blocker bugs, submit > patches, referee etc. But I would like to distinguish that from > release management and call it instead "directing the Sage project".
For what it's worth, I'd be interested in doing an efficient 4.2 release with the primary goal of getting the categories code in and trying to fix the issues on 10.6. --Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
