summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
authorCarl Worth <cworth@cworth.org>2006-02-13 16:47:01 -0800
committerCarl Worth <cworth@cworth.org>2006-02-13 16:47:01 -0800
commit6c38e238e5daab5df4c11027d28e48e62bbd4bc8 (patch)
tree150fc4b07ca1b92e8439bb722fde8bf63db7d009 /RELEASING
parent0b5ac24b1522b3287903c04fb894bfae4fc67403 (diff)
parent980eff38e494223de00e7ded706f6beaca27fce1 (diff)
Remove pixman from SNAPSHOT_0_4_0SNAPSHOT_0_4_0
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING24
1 files changed, 15 insertions, 9 deletions
diff --git a/RELEASING b/RELEASING
index 9088f9b5d..57f289dfc 100644
--- a/RELEASING
+++ b/RELEASING
@@ -39,15 +39,19 @@ fixes are committed. Here are the steps to follow:
4) Increment CAIRO_VERSION in configure.in
- Right now, in its pre-release form, we are incrementing
- CAIRO_VERSION for each snapshot but we are not changing
- the libtool shared library version information. Increment the
- subminor version for bug fixes and backwards-compatible
- additions to the API. Increment the minor number (and reset
- the subminor) for backward-incompatible changes to the API
- (including removals). Leave the major number at 0 until we are
- ready for the first 1.0 release, (at which point these rules
- will change).
+ First, remove the "-head" suffix, then increment the version
+ as follows:
+
+ If there are backward-incompatible changes in the API,
+ (function removals, or semantic changes), increment the minor
+ number and reset the sub-minor number to 0.
+
+ Otherwise, (that is, if there are only bug fixes and perhaps
+ API additions), then increment only the sub-minor number.
+
+ Prior to the initial "1.0" release of cairo, leave the major
+ number at 0. Also, do not modify the "libtool shared library
+ version" variables, (LT_CURRENT, LT_VERSION, LT_AGE).
5) Commit the changes to NEWS and configure.in
@@ -71,6 +75,8 @@ fixes are committed. Here are the steps to follow:
cvs tag SNAPSHOT_X_Y_Z
+8) Add a "-head" to CAIRO_VERSION in configure, and commit.
+
9) Send a message to cairo-announce@cairographics.org to announce the
new snapshot using the text provided from "make release-publish".