summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
authorSøren Sandmann Pedersen <sandmann@redhat.com>2009-02-06 18:01:57 -0500
committerSøren Sandmann Pedersen <sandmann@redhat.com>2009-02-06 18:01:57 -0500
commit6815e754d31d5a431028c8ca62911c07b753edc8 (patch)
treeccfb4cbb48fff5dbc67430678ba6d29bfbcdb2ab /RELEASING
parent6df6a43dc7119a510cf9db2e62fcc970a539e5a3 (diff)
Bump version number post-release
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING7
1 files changed, 2 insertions, 5 deletions
diff --git a/RELEASING b/RELEASING
index 7040deb..5a97b28 100644
--- a/RELEASING
+++ b/RELEASING
@@ -31,11 +31,7 @@ Here are the steps to follow to create a new pixman release:
4) Use "git commit" to record any changes made in steps 2 and 3.
-5) Generate the final tar files with
-
- make distcheck
-
- and publish the tar files by running
+5) Generate and publish the tar files by running
make PREV=<last version> GPGKEY=<your gpg key id> release-publish
@@ -57,6 +53,7 @@ Here are the steps to follow to create a new pixman release:
configure.ac. Commit this change, and push all commits created
during this process using
+ git push
git push --tags
You must use "--tags" here; otherwise the new tag will not