Skip to content

Commit

Permalink
RELEASING: Clarify snapshot numbering rules
Browse files Browse the repository at this point in the history
  • Loading branch information
Bryce Harrington committed Dec 11, 2015
1 parent 2dc0149 commit 6cd5a18
Showing 1 changed file with 15 additions and 12 deletions.
27 changes: 15 additions & 12 deletions RELEASING
Original file line number Diff line number Diff line change
Expand Up @@ -52,27 +52,30 @@ Here are the steps to follow to create a new cairo release:
development tree between Minor releases, as desired.

Cairo uses even numbers for official releases, and odd numbers
for development snapshots. Thus, for a Minor release the
version numbers should be:
for development snapshots. Thus, for a Minor release it would
be:

LAST_RELEASE="X.Y.Z" # e.g. 1.14.4
THIS_RELEASE="X.Y+2.0" # e.g. 1.16.0
LAST_RELEASE="X.Y.Z" # e.g. 1.12.0
THIS_RELEASE="X.Y+2.0" # e.g. 1.14.0

While for a micro release it would be:
While for a Micro release the version numbers should be:

LAST_RELEASE="X.Y.Z" # e.g. 1.16.0
THIS_RELEASE="X.Y.Z+2" # e.g. 1.16.2
LAST_RELEASE="X.Y.Z" # e.g. 1.14.0
THIS_RELEASE="X.Y.Z+2" # e.g. 1.14.2

Snapshots are similar but have odd minor versions, e.g.:
Snapshots are similar but have odd minor versions. Also, the
first snapshot release in a new series will be .2 rather than
.0, e.g.:

LAST_RELEASE="X.Y.Z" # e.g. 1.16.2
THIS_RELEASE="X.Y+1.0" # e.g. 1.17.0
LAST_RELEASE="X.Y.Z" # e.g. 1.14.0
THIS_RELEASE="X.Y+1.0" # e.g. 1.15.2

and subsequent snapshots in that series are just normal micro
releases:

LAST_RELEASE="X.Y.Z" # e.g. 1.17.0
THIS_RELEASE="X.Y.Z+2" # e.g. 1.17.2
LAST_RELEASE="X.Y.Z" # e.g. 1.15.2
THIS_RELEASE="X.Y.Z+2" # e.g. 1.15.4



4) Fill out an entry in the NEWS file
Expand Down

0 comments on commit 6cd5a18

Please sign in to comment.