summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
authorCarl Worth <cworth@cworth.org>2009-09-28 20:03:11 -0700
committerCarl Worth <cworth@cworth.org>2009-09-28 20:03:39 -0700
commit2841a4cd8c6c64fdf4b2203ab73b57b38a50f651 (patch)
treea3c9302ebc5f4dc2d847b8f6716d83fc0c86fce6 /RELEASING
parenta790aff4fef7d0c86b7b9c0da4afdc9c0aba6636 (diff)
Increment version to 2.9.02.9.0
And add a reminder to RELEASING that the incremented version number needs to be committed, (since I forgot to do this with 2.8.99.902).
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING3
1 files changed, 2 insertions, 1 deletions
diff --git a/RELEASING b/RELEASING
index e32ecf67..afc9f432 100644
--- a/RELEASING
+++ b/RELEASING
@@ -19,7 +19,8 @@ The process for releasing a new tarball is as follows:
3. Update your module version (usually found in configure.ac)
$ vi configure.ac # bump version
- $ git push origin # make sure you're on the release branch
+ $ git commit
+ $ git push origin # make sure you're on the release branch
4. Verify your module builds