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 "CreatingDerbyBranch" by RichardHillegas
Date Tue, 12 Oct 2010 18:54:29 GMT
Dear Wiki user,

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

The "CreatingDerbyBranch" page has been changed by RichardHillegas.
http://wiki.apache.org/db-derby/CreatingDerbyBranch?action=diff&rev1=1&rev2=2

--------------------------------------------------

  
   1. Post a message to derby-dev@db.apache.org requesting creation of a Hudson build job
for the new branch.
  
-  1. After creating the branch, bump the version number on '''trunk'''. There is not currently
an ant target for bumping the version number on the trunk so you need to edit `tools/ant/properties/release.properties`
on trunk by hand. Bump the major/minor properties as appropriate, zero out the maint property
(if it isn't zero already), and ensure the beta flag is set to true (if it isn't already).
E.g. after bumping from 10.4 to 10.5 `release.properties` should look similar to: 
+  1. After creating the branch, bump the version number on '''trunk'''. Again, from the root
directory of your code client, issue the following command: 
    {{{
+ ant writeReleaseProperties
+ }}}
+   (!) You will be prompted to enter a new release ID. Use 0 for the third and fourth numbers
of the id and add "beta" to the end. This will guarantee that distributions built from the
trunk will know that they are non-upgradable alpha versions. So for instance, "10.8.0.0 beta"
would be a legal release id for the trunk.
- #Wed Jul 19 08:21:42 PDT 2006
- drdamaint=0
- maint=0000000
- major=10
- minor=5
- eversion=10.5
- beta=true
- copyright.comment=Copyright 1997, 2008 The Apache Software Foundation or its licensors,
as applicable.
- vendor=The Apache Software Foundation}}}
-   (!) It is probably a good idea to update to the head of trunk, and do a clean build (`ant
clobber; ant all`) and run some tests before committing the change.
  
   1. Also consider bumping the version number for the upgrade tests on trunk at this time;
in method boot in java/engine/org/apache/derby/impl/sql/catalog/!DataDictionaryImpl.java,
modify the value for softwareVersion. But this can also be done the next time new upgrade
tests get added on trunk.
- 
-  1. <<Anchor(BranchVersion)>> On the '''new branch''', edit `tools/ant/properties/release.properties`
and update the value of the `maint` property. The exact value of depends on the type of release
(feature, update or snapshot). For a new feature release the value will typically be
-   {{{
- maint=1000000
- }}}
-   This will set the version string for the branch to 
-   {{{
- <major>.<minor>.1.0 (beta)
- }}}
-   The relationship between the `maint` property and the version number reported by `sysinfo`
is given by the following equation: `maint=100000*3rd+4th`, (or `maint=1000000*fixpack+point`
as described in the [[http://db.apache.org/derby/papers/versionupgrade.html|Derby Versioning
Scheme]]. Note that a "fixpack" of 0 overrides the `beta` property in `tools/ant/properties/release.properties`
and tags the version string with "alpha"). See also the description of how to [[#ReleaseCandidate|spin
a release candidate]].  
- 
-   (!) It is probably a good idea do a clean build (`ant clobber; ant all`) and run some
or all tests before committing this change to the branch.
- 
-   <!> For releases off branches older than 10.4, you need to first run ant regex (in
tools/release) to automatically update version references in a number of master files. These
changed master files also need to be checked in.
  
   1. Add the new branch number to the list of branches on the source page of the website.

    {i} For instructions on how to build the website using Forrest, please see: [[http://db.apache.org/derby/papers/derby_web.html]]
  
-   The actual page to modify is `src/documentation/content/xdocs/dev/derby_source.xml`. For
a minor (bug fix) release, consider bumping the third version of the source tree it will come
off (likely a branch).
+   The actual page to modify is `src/documentation/content/xdocs/dev/derby_source.xml`.
  

Mime
View raw message