Docutils Release Procedure

Authors: David Goodger
Lea Wiemann
open to all Docutils developers
Contact: docutils-develop@lists.sourceforge.net
Date: 2015-02-24
Revision: 7801
Copyright: This document has been placed in the public domain.

Assumptions and their failure

On the test machine python2.4, 2.5, 2.6, 2.7 and 3.2, 3.3, and 3.4 are installed. Some in /usr/ some under /usr/local.

Assumption: If python2.6 is in /usr/bin/ than site-packages is under
/usr/local/lib/python2.6.

On new ubuntu 12.10

Releasing

REWORK FOR SOURCEFORGE REPO

Steps in boldface text are not covered by the release script at sandbox/infrastructure/release.sh. "Not covered" means that you aren't even reminded of them.

Note

This document does not cover branching and tagging, but the release script does.

Note

You may want to use ReleaseForge instead of using SourceForge's file release system.

Call sandbox/infrastructure/release.sh new_version svn_version. For details see the script.

new_version is the current version, status will change from repository to release. svn_version is the version after release.

Note

BUG test tarball requires root password, but it is possible to skip this stage interactively, and testing should be done before release.