Put release commits on a new branch until published.
commit02d3a978c86b890759e4c10d3c13a40fd6a4d709
authorThomas Leonard <talex5@gmail.com>
Tue, 27 Nov 2007 20:22:30 +0000 (27 20:22 +0000)
committerThomas Leonard <talex5@gmail.com>
Tue, 27 Nov 2007 20:31:07 +0000 (27 20:31 +0000)
treec7d7ef42ecaaabdc9021590f731513cc0520c1df
parentc79ee9079826060f104c09d0cef02d5d28cc5aeb
Put release commits on a new branch until published.

We used to write two commits to version control during release (one
with the release version, and one to start the new snapshot series).
These would get reverted if the used failed the release.

The problem was that when bugs were found it was tempting to make
(and possibly commit) changes to this modified version. These changes
then had to be rebased to the point before the release.

Now, the two commits are made on a new temporary branch. HEAD remains
at its original location during release testing, so commits are against
the right version and go to the right place. Failing a build now only requires
changing the temporary branch. Publishing moves HEAD to the tip of the new
branch.
release.py
scm.py
support.py