summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
authorCarl Worth <cworth@cworth.org>2005-08-12 23:50:17 +0000
committerCarl Worth <cworth@cworth.org>2005-08-12 23:50:17 +0000
commita201637c7224b921948b79e4244dcc4f99f76cdf (patch)
tree56ae2748ac68f253329766c16b2989442f7596b1 /RELEASING
parent21dff93be5fd8fff1e4de96afaf8ff12cb7a850a (diff)
downloadcairo-a201637c7224b921948b79e4244dcc4f99f76cdf.tar.gz
Move tag from an instruction in RELEASING to an automated step at the end of release-publish.
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING9
1 files changed, 3 insertions, 6 deletions
diff --git a/RELEASING b/RELEASING
index d2904f523..979a631eb 100644
--- a/RELEASING
+++ b/RELEASING
@@ -74,15 +74,12 @@ fixes are committed. Here are the steps to follow:
* Create a LATEST-package-version file (after deleting any old one)
* Place local copies of both files in the releases directory
* Provide some text for the release announcement (see below).
+ * Tag the entire source tree with a tag of the form RELEASE_X_Y_Z
-7) Tag the entire source tree with a tag of the form RELEASE_X_Y_Z:
-
- cvs tag RELEASE_X_Y_Z
-
-8) Increment cairo_version_micro to the next larger (odd) number in
+7) Increment cairo_version_micro to the next larger (odd) number in
configure, and commit.
-9) Send a message to cairo-announce@cairographics.org and CC
+8) Send a message to cairo-announce@cairographics.org and CC
gnome-announce-list@gnome.org to announce the
new release using the text provided from "make release-publish".