Jeroen has been doing very nice release announcements summarizing the changes and people involved. For an example, see
https://groups.google.com/d/msg/sage-release/V5RVnB2sH88/zs8hXmUlkq8J It would be nice to keep that tradition, but also divide up the responsibilities to make the release process more sustainable. Maybe somebody wants to volunteer (*hint* *hint*) to write the release notes? The information is contained in the git commit history, it just needs to be presented in a concise way: $ git log --author "Release Manager" 6.0.rc1 ^6.0.rc0 --oneline 3cf92ba Trac #15529: Maxima takes version information from git repo 4ab6eba Trac #13015: Metaticket: revamp workflow / switch to git ab077f0 Trac #15509: sage-fix-pkg-checksums can break when not run from bash 15d89e9 Trac #15527: Automatically pick up version for bdist 40ed717 Trac #15526: banner is not updated 9531df5 Trac #15517: Run sage-upgrade *outside* of the Sage shell 3fc4257 Trac #15524: sage-fix-pkg-checksums does not preserve tarball name c23ec37 Trac #14715: Gracefully break upgrading from earlier versions $ git log --author "Release Manager" 6.0.rc1 ^6.0.rc0 commit 3cf92ba955bfe9789dbc336e8b02b4899403428a Merge: 4ab6eba 148fc58 Author: Release Manager <[email protected]> Date: Tue Dec 17 11:42:24 2013 +0000 Trac #15529: Maxima takes version information from git repo Maxima's configure.in checks if it is being run from a git repo, and if so then it uses `git describe --dirty` as maxima version. URL: http://trac.sagemath.org/15529 Reported by: vbraun Ticket author(s): Volker Braun Reviewer(s): R. Andrew Ohana commit 4ab6eba3c8aabdacd5d077155eb85d0df138e29d Author: Release Manager <[email protected]> Date: Tue Dec 17 00:05:34 2013 +0000 Trac #13015: Metaticket: revamp workflow / switch to git We plan to revamp the development workflow for Sage, involving a few separate (big) changes: * switch to git * consolidate our repositories into a single repository * simplified development interface We break down the steps needed for this transition in the following tasks/tickets: * #14480 - switch to new directory layout and update build system * #14481 - write a new developer manual; see https://github.com/sagemath/git-developer-guide * #14482 - write development scripts * Make sure the patchbot works with the new layout (this seems to be okay). * #15222 - `make download` to download all tarballs * #15221 - always rebuild packages if the version number changes * #15401 - Build git without gettext if necessary * #15420 - Borken git doctests. * #15430 - Enable cython caching * #15436 - Cksum uses tabs instead of spaces, breaking sage-spkg's regex * #15458 - "make distclean" fails on Solaris * #15465 - Allow using Sage without git repository * #15468 - update to latest upstream git * #15469 - Symmetrica spkg-check fails due to whitespace * #15472 - Fixes for the source tarball generation (sage -sdist) * #14968 - Store actual tarball name in pkg metadata. * #15517 - Run sage-upgrade *outside* of the Sage shell Instructions for using the new workflow: QuickStartSageGit URL: http://trac.sagemath.org/13015 Reported by: kini Ticket author(s): Reviewer(s): commit ab077f0b4017617e1e8d566d225661dff8c57cd5 Merge: 15d89e9 35fc693 Author: Release Manager <[email protected]> Date: Tue Dec 17 00:03:15 2013 +0000 Trac #15509: sage-fix-pkg-checksums can break when not run from bash just a silly typo URL: http://trac.sagemath.org/15509 Reported by: ohanar Ticket author(s): R. Andrew Ohana Reviewer(s): Volker Braun commit 15d89e9d06fd150be0fc741884a8039e9fcac6aa Merge: 40ed717 7673476 Author: Release Manager <[email protected]> Date: Mon Dec 16 22:54:25 2013 +0000 Trac #15527: Automatically pick up version for bdist URL: http://trac.sagemath.org/15527 Reported by: vbraun Ticket author(s): Volker Braun Reviewer(s): R. Andrew Ohana commit 40ed717359843bbc927a7e034124499929121428 Merge: 9531df5 40446e2 Author: Release Manager <[email protected]> Date: Mon Dec 16 22:54:03 2013 +0000 Trac #15526: banner is not updated Starting up sage-6.0.rc0 still shows the wrong version. URL: http://trac.sagemath.org/15526 Reported by: vbraun Ticket author(s): Volker Braun Reviewer(s): Volker Braun commit 9531df536d6af2b00e71ac8f60c7ec3b8cdd0377 Merge: 3fc4257 1f27435 Author: Release Manager <[email protected]> Date: Mon Dec 16 22:53:30 2013 +0000 Trac #15517: Run sage-upgrade *outside* of the Sage shell Running `make` inside a Sage shell doesn't really work well, because `sage-env` isn't resourced during the build. This breaks upgrading if new packages are installed in the upgrade which require environment variable changes. Most of the old work-arounds in `spkg/install` removed in #14715 existed precisely for this reason. Now that nothing can upgrade '''to''' Sage 6.0, we should make sure that upgrading '''from''' Sage 6.0 doesn't suffer this problem. URL: http://trac.sagemath.org/15517 Reported by: jdemeyer Ticket author(s): Jeroen Demeyer Reviewer(s): Volker Braun, R. Andrew Ohana commit 3fc425778e2ae62158adbde8282d556ef2bb388b Merge: c23ec37 58b7f93 Author: Release Manager <[email protected]> Date: Mon Dec 16 22:39:41 2013 +0000 Trac #15524: sage-fix-pkg-checksums does not preserve tarball name This is a followup to #14968 URL: http://trac.sagemath.org/15524 Reported by: vbraun Ticket author(s): Volker Braun Reviewer(s): commit c23ec373aae2ce5bfd66a539311ffa58130fd398 Merge: 68680e9 cd83bc9 Author: Release Manager <[email protected]> Date: Mon Dec 16 18:04:19 2013 +0000 Trac #14715: Gracefully break upgrading from earlier versions If older versions of Sage try to upgrade to Sage 6.0, this should break gracefully. There should be a nice message explaining that it cannot be done, perhaps pointing to [http://boxen.math.washington.edu/home/release/sage-5.13/] where the upgrade to Sage 5.13 can be done. URL: http://trac.sagemath.org/14715 Reported by: jdemeyer Ticket author(s): Jeroen Demeyer Reviewer(s): Volker Braun -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
