diff options
| author | Carl Worth <cworth@cworth.org> | 2005-08-13 05:00:20 +0000 |
|---|---|---|
| committer | Carl Worth <cworth@cworth.org> | 2005-08-13 05:00:20 +0000 |
| commit | b3a4f29f830dbcb57ef3d1e4c3c140126752043b (patch) | |
| tree | b69f9d850354f0134bd300bdc2a04a84ff0993b2 /RELEASING | |
| parent | 3f24b949a070aebaeaa465ccd09604bda0be717b (diff) | |
Added notes for release 0.9.2.RELEASE_0_9_2
Increment CAIRO_VERSION to 0.9.2 and libtool versioning to 3:1:1.
Remove some more 'snapshot' language. Make it more clear that the libtool versioning numbers need to be updated.
Diffstat (limited to 'RELEASING')
| -rw-r--r-- | RELEASING | 10 |
1 files changed, 3 insertions, 7 deletions
@@ -1,9 +1,4 @@ -So far, cairo hasn't reached an initial release. But we can still form -good habits now by practicing the release process with the current -snapshots. - -A new snapshot is needed whenever significant new features or bug -fixes are committed. Here are the steps to follow: +Here are the steps to follow to create a new cairo release: 1) Ensure that there are no local, uncommitted modifications. The best thing to do here may be to begin with a fresh checkout from CVS: @@ -39,7 +34,8 @@ fixes are committed. Here are the steps to follow: find src/ -name '*.h' -not -name '*-private.h' -not -name 'cairoint.h' | \ xargs cvs diff -r RELEASE_X_Y_Z -4) Increment cairo_version_{minor|micro} in configure.in: +4) Increment cairo_version_{minor|micro} and LT_{CURRENT|VERSION|AGE} + in configure.in: If there are backward-incompatible changes in the API, stop now and don't release. Go back and fix the API instead. Cairo |