From bae5db893f20eaf9c8ec56057617a8ce800cce48 Mon Sep 17 00:00:00 2001 From: =?utf8?q?S=C3=B8ren=20Sandmann=20Pedersen?= Date: Mon, 9 Jun 2008 13:06:50 -0400 Subject: [PATCH] Post-release version bump --- RELEASING | 18 ------------------ configure.ac | 2 +- 2 files changed, 1 insertion(+), 19 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 diff --git a/configure.ac b/configure.ac index f64d4b2..52ecb0d 100644 --- a/configure.ac +++ b/configure.ac @@ -57,7 +57,7 @@ AC_PREREQ([2.57]) m4_define([pixman_major], 0) m4_define([pixman_minor], 11) -m4_define([pixman_micro], 4) +m4_define([pixman_micro], 5) m4_define([pixman_version],[pixman_major.pixman_minor.pixman_micro]) -- 2.7.4