diff options
| author | Behdad Esfahbod <behdad@behdad.org> | 2008-08-28 18:18:23 -0400 |
|---|---|---|
| committer | Behdad Esfahbod <behdad@behdad.org> | 2008-08-28 18:18:23 -0400 |
| commit | 894940b81f0272a2993d3a785fd505b3a4375e6e (patch) | |
| tree | 82ab202956fd234f3e4225318e55d2ad9aa06fe8 /RELEASING | |
| parent | ab5c528de2fc744d77c44ea1a9a3467f1ec5f81d (diff) | |
Some nasty tracks to make changing version number not cause a total rebuild
Quite slick! This comes handy when git-bisect'ing. The canonical version
number is in toplevel cairo-version.h now.
Diffstat (limited to 'RELEASING')
| -rw-r--r-- | RELEASING | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -54,7 +54,7 @@ Here are the steps to follow to create a new cairo release: find src/ -name '*.h' ! -name '*-private.h' ! -name 'cairoint.h' ! -name 'cairo-features-win32.h' | \ xargs git diff X.Y.Z.. -- -4) Increment cairo_version_{minor|micro} in src/cairo-version.h: +4) Increment cairo_version_{minor|micro} in cairo-version.h: If there are backward-incompatible changes in the API, stop now and don't release. Go back and fix the API instead. Cairo @@ -70,7 +70,7 @@ Here are the steps to follow to create a new cairo release: Otherwise, (ie. there are only bug fixes), increment cairo_version_micro to the next larger (even) number. -5) Commit the changes to NEWS and src/cairo-version.h +5) Commit the changes to NEWS and cairo-version.h It's especially important to mention the new version number in your commit log. @@ -98,7 +98,7 @@ Here are the steps to follow to create a new cairo release: prints it for you. 7) Increment cairo_version_micro to the next larger (odd) number in - src/cairo-version.h, commit, and push. + cairo-version.h, commit, and push. 8) Push the newly created tag out to the central tree with a command something like: |