Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Wed, 12 Mar 2008 20:04:55 -0000
Message-ID: <20080312200455.25112.23740@eos.apache.org>
Subject: [Db-derby Wiki] Update of "DerbySnapshotOrRelease" by DyreTjeldvoll

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

------------------------------------------------------------------------------
  
  ==== Work the toward a release candidate ====
  
-  1. Arrange for the version in JIRA; See section titled 'JIRA version maintenance'.
+  1. Arrange for the version in JIRA; See section titled 'JIRA version maintenance'. /!\ '''There is no such section in this page? Overlaps with item in previous section?''' -dt /!\
  
   1. Target the bugs you feel should be fixed in JIRA
  
@@ -213, +213 @@

  
    To build the documentation, you need to obtain DITA-OT1.1.2.1_bin-ASL.zip and place it in the docs' tree lib. See: [http://db.apache.org/derby/manuals/dita.html] for more info about building the documentation.
  
- === For each release candidate === [[Anchor(ReleaseCandidate)]]
+ [[Anchor(FirstRC)]]
+ === For the first release candidate ===
+  1. Set the beta property to false.
+  1. Create `maintversion.properties`. 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}}}
+  1. Check in the new version.
+ 
+ [[Anchor(ForEachRC)]]
+ === For each release candidate ===
  
  ==== Check-ins just before generating release artifacts ====
  
-  1. For the '''first''' release candidate on a branch: Set the beta property to false and create `maintversion.properties`, and check in the new version of `release.properties`.
+  1. /!\ '''Check in the new version number after RC is spun?''' For the '''first''' release candidate on a branch:  and create , and check in the new version of `release.properties`.
  
-   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:
+   /!\ '''This really belongs further down, where preparations for the next RC is made?''' 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
@@ -229, +238 @@

  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}}}
  
    You will need to clobber and build again before you can see the changed release number(s) reflected in the source. Note that the first release off a new branch is automatically beta, even if you set the beta flag in tools/ant/properties/release.properties to false. Also adjust version numbers in documentation by modifying the appropriate *conrefs.dita files.