On Fri, Jun 19, 2009 at 12:00:19PM -0700, Tom Boothby wrote:
> I'm the release manager for sage-4.0.3.
> Python to 2.6, and if I succeed, I'll rename the release to sage-4.1.
> In about an hour, I'm going to send out review requests.

Tom: thanks very much for your time on this!

To all (potential) category code reviewers: I would really want to see
the category code end up in 4.1. FPSAC, the main algebraic
combinatorics conference, is less than one month from now, and the
sage-combinat dev have invested a lot of work this year to get Sage up
to speed at this point. We have 1/2 Mb worth of combinatorics patches
(root systems, crystals, symmetric functions, ...) waiting for the
category code to get in. For those, we will be able to manage the
review process among us, but we will need some time.

One year ago, we were promised full support from the Sage team. Here
is the time were we need you most guys!

Thanks much in advance,
                                Nicolas

PS 1: a personal point of view for the reviewers: the new category
code is certainly far from perfect. Yet, I think the reviewing goal
should concentrate on making sure that the Sage rules are satisfied
(100% doctests, ...) and that there is no complete show stopper. I am
eagerly looking forward further comments and suggestions for
improvements. However, given the difficulty of maintaining this patch
bomb outside of Sage, and given the amount of code that depends on it,
those should be left for later patches. Release early, release often.


PS 2: I'll be on vacations June 28th -> July 4th; I'll also be pretty
busy moving back to France July 8th - 19th.

--
Nicolas M. ThiƩry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to