diff options
| author | Carl Worth <cworth@cworth.org> | 2006-04-25 08:54:59 -0700 |
|---|---|---|
| committer | Carl Worth <cworth@cworth.org> | 2006-04-25 08:54:59 -0700 |
| commit | 3d6cdc996f3a3f4d54d0d8926daa3973d69e4dc2 (patch) | |
| tree | c910e8172b2e92cd3c137d57aa00a1099ea5ccd7 /RELEASING | |
| parent | 68c5382b6cdc442f3057b8e4eed2dfe7084ef7f1 (diff) | |
Add release vs. snapshot distinction to version increment instructions
Diffstat (limited to 'RELEASING')
| -rw-r--r-- | RELEASING | 5 |
1 files changed, 3 insertions, 2 deletions
@@ -44,8 +44,9 @@ Here are the steps to follow to create a new cairo release: So cairo_version_major will not be incremented unless we come up with a new versioning scheme to take advantage of it. - If there are API additions, then increment - cairo_version_minor and reset cairo_version_micro to 0. + If there are API additions, then increment cairo_version_minor + and reset cairo_version_micro to 0. NOTE: The minor version is + only incremented for releases, not for snapshots. Otherwise, (ie. there are only bug fixes), increment cairo_version_micro to the next larger (even) number. |