about summary refs log tree commit diff
path: root/doc/dev
diff options
context:
space:
mode:
authorEelco Dolstra <e.dolstra@tudelft.nl>2006-10-06T13·45+0000
committerEelco Dolstra <e.dolstra@tudelft.nl>2006-10-06T13·45+0000
commit7bada48b36a091bb30c905229e16df3c36c90d7d (patch)
tree82304a0481c6ee0a620afaa0a7a8091b3133c546 /doc/dev
parente1cc84259ce38f0639f6304f04e1747c00fd43cb (diff)
* Bumped the version number to 0.11.
Diffstat (limited to 'doc/dev')
-rw-r--r--doc/dev/release-procedures.txt7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/dev/release-procedures.txt b/doc/dev/release-procedures.txt
index deccb1091006..1e95a9ee9aca 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.