summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
authorBehdad Esfahbod <behdad@behdad.org>2007-03-03 15:34:19 -0500
committerBehdad Esfahbod <behdad@behdad.org>2007-03-03 15:34:19 -0500
commit57e1b6fa98d688b72dd3617e8313ea35f8ce78e1 (patch)
treee4fffc73a0cd7a073187e48e744957d984c8d652 /RELEASING
parent052acc95e9c354981eea0968c5727e4a0568a959 (diff)
[RELEASING] Reorder pushing tag and commits
We should push the tag only after pushing the actually release commit.
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING8
1 files changed, 4 insertions, 4 deletions
diff --git a/RELEASING b/RELEASING
index e71bc07e..079bf835 100644
--- a/RELEASING
+++ b/RELEASING
@@ -92,14 +92,14 @@ Here are the steps to follow to create a new cairo release:
If for some reason you lost this message, "make release-publish-message"
prints it for you.
-7) Push the newly created tag out to the central tree with a command
+7) Increment cairo_version_micro to the next larger (odd) number in
+ configure, commit, and push.
+
+8) Push the newly created tag out to the central tree with a command
something like:
git push cairo X.Y.Z
-8) Increment cairo_version_micro to the next larger (odd) number in
- configure, commit, and push.
-
9) Edit the cairo bugzilla product and add the new version numbers
10) Send a message to cairo-announce@cairographics.org and CC