Dear Sage lovers,
I'm here at the Sage-GIT workshop and it's very clear that the switch to
GIT is happening.
The current idea is to have Sage 5.9 and Sage 5.10 with the current
Mercurial-based workflow. Hopefully before Sage 5.10, there will already
be a usable GIT-based release in parallel with the Mercurial release.
This won't have all features yet, but it should be possible to use for
development (for those who know it). If needed, there will be further
Sage 5.1x releases until the GIT development scripts are ready. Sage 6.0
will then be a release which is only about switching to GIT (no other
non-GIT-related tickets).
Sage 5.1x will also be the last release under my release management. The
switch to GIT is an excellent time for a new release manager, since the
release workflow will change substantially anyway. Robert Bradshaw has
agreed to be release manager for Sage 6.0. He doesn't want to do further
releases, so we need volunteers for release management for Sage 6.1 and
later.
Cheers,
Jeroen.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
