db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "ReleaseCandidates" by BryanPendleton
Date Tue, 11 Oct 2016 01:51:20 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "ReleaseCandidates" page has been changed by BryanPendleton:

   * Version number is correct. On the 10.6 and earlier branches, the version number should
have been bumped after spinning the previous release candidate.
  You may need to worry about the following arcana if you are building a release on a 10.6
or earlier branch: The third and fourth parts of the version number are combined into a single
property, maint, where maint = (third digit * 1000000) + fourth digit. Note that removing
the beta flag will not have an effect unless the 3rd digit (fixpack) is greater than 0, since
version numbers with fixpack=0 always are considered alpha. Fixpack (3rd digit) will normally
be set to 1 when the branch is cut, but if it isn't, it must be incremented before the release
candidate can be created. 
+ ==== Managing version numbers in JIRA ====
+ Careful management of the JIRA release versions enables us to track the particular issues
that were fixed in each particular release, even release ''candidates''.
+ It's perhaps easiest to explain with an example:
+ 1. RENAME to be This will automagically associate the release with
all bugs which have been fixed for 10.13.
+ 1. Create a new release id to represent the head of the 10.13 branch after the
release goes GA.
+ Note that you have to adjust the 10.13 ids every time you create a new release candidate.
But the idea is that, when the release is finished, its id will be
+    10.13.1.x
+ and the head of the 10.13 branch will be advanced to
+    10.13.1.(x+1)
  ==== Check-ins just before generating release artifacts ====

View raw message