summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING10
1 files changed, 3 insertions, 7 deletions
diff --git a/RELEASING b/RELEASING
index 3dfe29bb..ac306fce 100644
--- a/RELEASING
+++ b/RELEASING
@@ -54,8 +54,7 @@ Here are the steps to follow to create a new cairo release:
find src/ -name '*.h' ! -name '*-private.h' ! -name 'cairoint.h' ! -name 'cairo-features-win32.h' | \
xargs git diff X.Y.Z.. --
-4) Increment cairo_version_{minor|micro} and LT_{CURRENT|VERSION|AGE}
- in configure.in:
+4) Increment cairo_version_{minor|micro} in src/cairo-version.h:
If there are backward-incompatible changes in the API, stop
now and don't release. Go back and fix the API instead. Cairo
@@ -71,10 +70,7 @@ Here are the steps to follow to create a new cairo release:
Otherwise, (ie. there are only bug fixes), increment
cairo_version_micro to the next larger (even) number.
- Adjust LT_CURRENT, LT_VERSION, and LT_AGE as described in the
- comments in configure.in.
-
-5) Commit the changes to NEWS and configure.in
+5) Commit the changes to NEWS and src/cairo-version.h
It's especially important to mention the new version number in your
commit log.
@@ -102,7 +98,7 @@ Here are the steps to follow to create a new cairo release:
prints it for you.
7) Increment cairo_version_micro to the next larger (odd) number in
- configure, commit, and push.
+ src/cairo-version.h, commit, and push.
8) Push the newly created tag out to the central tree with a command
something like: