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 "DerbySnapshotOrRelease" by DyreTjeldvoll
Date Tue, 11 Mar 2008 16:17:54 GMT
Dear Wiki user,

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

The following page has been changed by DyreTjeldvoll:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
  svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/docs/trunk/ https://svn.apache.org/repos/asf/db/derby/docs/branches/{branchname}/
-m "Created the {branchname} doc branch"}}}
  
  
-  1. After creating the branch, bump the version number on the '''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):
+  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):
  
    {{{vi tools/ant/properties/release.properties
  }}}
  
-   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 or all tests before committing the change.
+   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. Then, '''on the new branch''', use the `bumplastdigit` ant target to set the `maint`
property. This target is only available in the `tools/release` directory:
+ /!\ '''Under construction''' /!\ 
  
-   {{{cd tools/release 
- ant bumplastdigit}}}
+  1. 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").  
  
-   If you look at `tools/ant/properties/release.properties` again you should see that the
`maint` property has been updated. 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.
+   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.
  
   1. Post to derby-dev requesting that a new version be added to JIRA for the next version
of Derby (this may well have been done earlier).
  

Mime
View raw message