1 Here are the steps to follow to create a new pixman release:
3 1) Ensure that there are no uncommitted changes or unpushed commits,
4 and that you are up to date with the latest commits in the central
5 repository. Here are a couple of useful commands:
7 # This should report "nothing to commit (working directory clean")
10 # This should give no output, (note there are *3* dots)
11 git log master...origin
13 2) Verify that the code passes "make distcheck".
15 NOTE: There is some test code in the test directory, but it's
16 not yet integrated into "make distcheck" yet. It might be
17 useful to run those programs, (but I don't know how to
18 interpret those results). Another very useful thing to do is
19 to run the cairo test suite against pixman. This can be done
20 by running the following commands with the latest cairo
23 tar xzf cairo-X.Y.Z.tar.gz
25 CAIRO_TEST_TARGET=image make test
27 4) Increment pixman_{major|minor|micro} in configure.ac according to
28 the directions in that file. Also note that if there is an ABI
29 change then there is further work to be done, (also described in
32 5) Use "git commit" record any changes made in steps 3 and 4.
34 6) Generate the final tar files with
38 And publish the tar files to everywhere appropriate.
40 Note: There's a "make release-publish" target to help with this
41 step, (creating the tar file and publishing it), but it depends on
42 getting gpg setup first. It's probably the right way to go in the
45 7) Increment pixman_micro to the next larger (odd) number in
46 configure.ac. Commit this change, and push all commits created
49 8) Send email announcements of the release to everywhere appropriate.