2004-04-06 20:13:11 +00:00
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
10 easy steps to creating a new cairo snapshot
|
|
|
|
|
==============================================
|
|
|
|
|
|
|
|
|
|
1) Commit code with a significant new feature or backwards
|
|
|
|
|
incompatibility.
|
|
|
|
|
|
|
|
|
|
Either of these events triggers the need for a new snapshot.
|
|
|
|
|
Users of cairo snapshots need to be able to specify snapshot
|
|
|
|
|
version numbers in order to get access to a specific set of
|
|
|
|
|
features.
|
|
|
|
|
|
2004-05-11 08:19:47 +00:00
|
|
|
2) Increment CAIRO_VERSION in configure.in
|
|
|
|
|
|
|
|
|
|
Right now, in its pre-release form, we are incrementing
|
|
|
|
|
CAIRO_VERSION for each snapshot but we are not changing the
|
|
|
|
|
libtool shared library version information. Until now, we've
|
|
|
|
|
only incremented the sub-minor version. We'll invent rules for
|
|
|
|
|
incrementing major and minor numbers when the time is right.
|
|
|
|
|
|
|
|
|
|
3) Verify that the code passes "make distcheck"
|
2004-04-06 20:13:11 +00:00
|
|
|
|
|
|
|
|
Running "make distcheck" should result in no warnings or
|
|
|
|
|
errors and end with a message of the form:
|
|
|
|
|
|
|
|
|
|
=============================================
|
|
|
|
|
cairo-X.Y.Z.tar.gz is ready for distribution
|
|
|
|
|
=============================================
|
|
|
|
|
|
|
|
|
|
(But the tar file isn't actually ready yet, as we still have
|
|
|
|
|
some more steps to follow).
|
|
|
|
|
|
2004-05-11 08:19:47 +00:00
|
|
|
4) Fill out an entry in the NEWS file
|
2004-04-06 20:13:11 +00:00
|
|
|
|
|
|
|
|
Sift through the information in ChangeLog since the last
|
|
|
|
|
snapshot. Summarize major changes briefly in a style similar
|
2004-05-11 08:19:47 +00:00
|
|
|
to other entries in NEWS. Take special care to note any
|
|
|
|
|
incompatible changes in the API. These should be easy to find
|
|
|
|
|
by looking for cairo.h in the ChangeLog.
|
2004-04-06 20:13:11 +00:00
|
|
|
|
|
|
|
|
5) Commit the changes to NEWS and configure.in
|
|
|
|
|
|
|
|
|
|
Don't forget to fill out the ChangeLog just like with any
|
|
|
|
|
other commit. It's especially important to mention the new
|
|
|
|
|
version number in the ChangeLog.
|
|
|
|
|
|
2004-05-11 08:19:47 +00:00
|
|
|
6) Run "make distcheck" to generate the final tar file including the
|
|
|
|
|
changes to NEWS and ChangeLog.
|
2004-04-06 20:13:11 +00:00
|
|
|
|
|
|
|
|
7) Copy the resulting tar file to the cairo snapshots distribution
|
|
|
|
|
directory:
|
|
|
|
|
|
|
|
|
|
scp cairo-X.Y.Z-tar.gz cairographics.org:/home/www/cairo/snapshots
|
|
|
|
|
|
|
|
|
|
8) Tag the entire source tree with a tag of the form SNAPSHOT_X_Y_Z:
|
|
|
|
|
|
|
|
|
|
cvs tag SNAPSHOT_X_Y_Z
|
|
|
|
|
|
|
|
|
|
9) Send a message to cairo-announce@cairographics.org to announce the
|
|
|
|
|
new snapshot.
|
|
|
|
|
|
2004-04-07 11:03:40 +00:00
|
|
|
The message should provide the URL for the snapshot:
|
2004-04-06 20:13:11 +00:00
|
|
|
|
2004-04-07 11:03:40 +00:00
|
|
|
http://cairographics.org/snapshots/cairo-X.Y.Z.tar.gz
|
|
|
|
|
|
|
|
|
|
and should also include the relevant section from the NEWS
|
|
|
|
|
file.
|
|
|
|
|
|
|
|
|
|
10) Sit back and relax in confidence, or alternately, brace yourself
|
|
|
|
|
for a flood of new bug reports.
|