From 7bada48b36a091bb30c905229e16df3c36c90d7d Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Fri, 6 Oct 2006 13:45:29 +0000 Subject: [PATCH] * Bumped the version number to 0.11. --- configure.ac | 2 +- doc/dev/release-procedures.txt | 7 +++++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/configure.ac b/configure.ac index ac9b54ddd..3054abee6 100644 --- a/configure.ac +++ b/configure.ac @@ -1,4 +1,4 @@ -AC_INIT(nix, 0.10) +AC_INIT(nix, 0.11) AC_CONFIG_SRCDIR(README) AC_CONFIG_AUX_DIR(config) AM_INIT_AUTOMAKE([dist-bzip2 foreign]) diff --git a/doc/dev/release-procedures.txt b/doc/dev/release-procedures.txt index deccb1091..1e95a9ee9 100644 --- a/doc/dev/release-procedures.txt +++ b/doc/dev/release-procedures.txt @@ -1,5 +1,8 @@ To produce a `stable' release from the trunk: +-1. Update the release notes; make sure that the release date is + correct. + 0. Make sure that the trunk builds in the release supervisor. 1. Branch the trunk, e.g., `svn cp .../trunk @@ -22,8 +25,8 @@ To produce a `stable' release from the trunk: branch (e.g., `.../branches/0.5') should be created from the original revision of the trunk (since maintenance releases should also be tested first; hence, we cannot have `STABLE=1'). The same - procedure can then be followed to produce maintenance release; just - substitute `.../branches/VERSION' for the trunk. + procedure can then be followed to produce maintenance releases; + just substitute `.../branches/VERSION' for the trunk. 7. Switch back to the trunk.