summaryrefslogtreecommitdiff
path: root/RELEASING
diff options
context:
space:
mode:
authorSøren Sandmann Pedersen <sandmann@daimi.au.dk>2008-06-09 13:06:50 -0400
committerSøren Sandmann Pedersen <sandmann@daimi.au.dk>2008-06-09 13:06:50 -0400
commitbae5db893f20eaf9c8ec56057617a8ce800cce48 (patch)
tree0b0279aefe02cf10b730b63e5eb238f24b525d94 /RELEASING
parent88e02d36792d3ad2615a775c9d21136c760087ef (diff)
Post-release version bump
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING18
1 files changed, 0 insertions, 18 deletions
diff --git a/RELEASING b/RELEASING
index 330e5e3..34d549b 100644
--- a/RELEASING
+++ b/RELEASING
@@ -24,24 +24,6 @@ Here are the steps to follow to create a new pixman release:
cd cairo
CAIRO_TEST_TARGET=image make test
-3) Fill out an entry in the NEWS file
-
- Sift through the logs since the last release. This is most
- easily done with a command such as:
-
- git log --stat pixman-X.Y.Z..
-
- where X.Y.Z is the previous release version.
-
- Summarize major changes briefly in a style similar to other
- entries in NEWS. Take special care to note any additions in
- the API. These should be easy to find by noting modifications
- to pixman.h in the log command above. And more specifically,
- the following command will show each patch that has changed the
- public header file since the given version:
-
- git log -p pixman-X..Z.. -- pixman/pixman.h
-
4) Increment pixman_{major|minor|micro} in configure.ac according to
the directions in that file. Also note that if there is an ABI
change then there is further work to be done, (also described in