Just a quick note: on two different systems, upgrading from alpha0 has mercurial put me in commit mode with something like:
HG: changed sage-banner HG: changed sage-gdb-commands HG: changed sage-maxima.lisp HG: changed sage-verify-pyc Could it be that one of the repositories had uncommited changes? Best, Alex On Mon, 1 Feb 2010 19:03:44 +1100, Minh Nguyen <[email protected]> wrote: > This is a rather quick release since Sage 4.3.2.alpha0. The original > plan was for Sage 4.3.2 to be out a few days before Sage Days 20. > However, the schedule for the final release has been shifted [1] to > Saturday 06th February 2010, Pacific time. The upcoming rc0 release is > strictly for bug fixes. A major new feature in this release is having > Dan Drake's SageTeX package in the standard spkg repository. > -- Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne -- Australia -- http://www.ms.unimelb.edu.au/~aghitza/ -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
