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 20:45:30 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

------------------------------------------------------------------------------
  
   1. Set the beta property to false. Bump the point (4th digit) if required, and check in
the new version. 
  
-   The third and fourth parts of the version are combined into a single property, maint,
where maint = (third digit * 1000000) + fourth digit. Also, if this is a major/minor (feature)
release, you should remove the beta flag at this time. 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. For feature releases fixpack (3rd digit) will
normally be set to 1 when the [#BranchCutting branch is cut], but if it isn't, it must be
incremented before the release candidate can be created. It will usually ''not'' be necessary
to bump point (4th digit) for the ''first'' release candidate, but this step is obviously
required for later release candidates. /!\ You should update tools/ant/properties/release.properties
by hand and then run:
+   The third and fourth parts of the version are combined into a single property, maint,
where maint = (third digit * 1000000) + fourth digit. Also, if this is a major/minor (feature)
release, you should set the beta property to false at this time. 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 [#BranchCutting branch is cut], but if it isn't, it must be incremented before
the release candidate can be created. It will usually ''not'' be necessary to bump point (4th
digit) for the ''first'' release candidate, but this step is obviously required for later
release candidates. E.g. for the ''second'' 10.4 release candidate, `release.properties` would
look something like:
+   {{{#Wed Jul 19 08:21:42 PDT 2006
+ drdamaint=0
+ maint=1000001
+ major=10
+ minor=4
+ eversion=10.4
+ beta=false
+ copyright.comment=Copyright 1997, 2008 The Apache Software Foundation or its licensors,
as applicable.
+ vendor=The Apache Software Foundation}}}
+ /!\ You should update tools/ant/properties/release.properties by hand and then run:
    {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties

  tools/release/maintversion.properties}}}
  

Mime
View raw message