> What needs to happen to go from 2.9.1.alpha2 to a release
> candidate and a release?
>
>  -- William

1. I would like to get patches in for all the critical tickets. In
particular, I'd like to see #1366 fixed up.

2. The following tickets could use review:
#1130, #1155, #1371, #1413, #1418, #1448, #1485, #1505, (#1516 &
#1536), #1533, #1558, #1561, (#1567 & #1568)
Also, I think Robert Bradshaw is currently reviewing #980. It would be
good to get at least a majority of these reviewed before Saturday.

3. Tickets #1495 & #1547 should also get patches soon, to improve the
way ATLAS builds.

4. At least by 2.9.2, we should have a pretty robust system for jmol.
I know there are one or two issues left, including #1580...

The plan is to do an rc0 by about 2:00am EST 12/22, then a release by
2am the next day.

-- Robert M
--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---

Reply via email to