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 Thu, 13 Mar 2008 12:24:15 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

------------------------------------------------------------------------------
  
  [[Anchor(FirstRC)]]
  === For the first release candidate ''on a new branch'' ===
+ 
-  1. Update `tools/ant/properties/release.properties` by hand, and set the beta property
to false.
+  1. Update `tools/ant/properties/release.properties` by hand, and set the `beta` property
to false.
   1. Create `maintversion.properties`, by running:
    {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties

  tools/release/maintversion.properties}}}
-   This step will ''not modify any files under version contro'' but the unversioned `maintversion.properties`
when [# building the release]
+   This step will ''not'' modify any files under version control, but you will need the unversioned
`maintversion.properties` when you [#CreateDistros create the distributions] later on.
-  1. Check in the new version.
+  1. Check in the modification.
+  1. You will need to clobber and build again before you can see the changed `beta` property
reflected in the source. Note that the first release off a new branch is automatically beta,
even if you set the `beta` property to false.
  
  [[Anchor(ForEachRC)]]
  === For each release candidate ===
  
  ==== Check-ins just before generating release artifacts ====
  
+  1. Verify that 
+   * `beta` property is false
+   * Version number is correct
-  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`.
+   * /!\ '''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`.
  
+  1. Also adjust version numbers in documentation by modifying the appropriate *conrefs.dita
files.
-   /!\ '''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
- 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 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.
  
   1. Generate RELEASE_NOTES.html in the branch and check it into the svn repository.
  
@@ -277, +270 @@

  
    The documentation needs to be included in the -bin distribution and src, so you will need
to access the doc branch when running the ant release target. The doc build is not controlled
by the source tree build, and thus needs to be completed beforehand. Information on building
the docs is located at [http://db.apache.org/derby/manuals/dita.html]. 
  
-  1. [[Anchor(CreateDistro)]]Create the distributions for release by running:
+  1. [[Anchor(CreateDistros)]]Create the distributions for release by running:
  
    {{{svn up
  ant clobber
@@ -357, +350 @@

   1. Bump the fourth digit of the source in preparation for a possible next build
    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}}}
- 
+   /!\ '''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
+ 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}}}
+  
   1. Post the distributions
  
    Copy the files from tools/release to your public_html directory on people.apache.org.
Post to derby-dev so that  others can begin testing.

Mime
View raw message