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, 18 Mar 2008 14:16:33 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

------------------------------------------------------------------------------
  #sane=<sane should *not* be set>}}}
  
  Special consideration for non-linux users:
+   * [#CopyPkgTmpl ant sign], the last step in the ant release process, may not work. Try
it out before the release time is there; if you cannot do this, you may achieve the same using
[#SignOne this script]. 
-   * [#CopyPkgTmpl `ant sign`], the last step in the ant release process, may not work.
-   try it out before the release time is there; if you cannot do this, you may achieve the
same using [#SignOne this script]. 
    * Similarly, you may use a script to verify the release
-   * Your md5 tool may be different.
-   you'll need to [#CopyPkgTmpl copy the file packaging.tmpl to packaging.properties and
adjust it appropriately].
+   * Your md5 tool may be different. You'll need to [#CopyPkgTmpl copy the file packaging.tmpl
to packaging.properties and adjust it appropriately].
  
  ==== Steps to prepare your machine/code check-out for the release process ====
  
@@ -179, +177 @@

    * The OSGi support (osgi.jar or felix.jar. Felix.jar should be automatically present in
tools/java with 10.4 and later).
    * The JSR169 support
  
-  1. [[Anchor(CopyPkgTmpl)]]Copy tools/ant/properties/packaging.tmpl to tools/ant/properties/packaging.properties
and modify as necessary.
+  1. [[Anchor(CopyPkgTmpl)]]Copy `tools/ant/properties/packaging.tmpl` to `tools/ant/properties/packaging.properties`
and modify as necessary.
  
-   The build will attempt to use a file called tools/ant/properties/packaging.properties
to carry out checksum (md5)and signing (pgp) tasks. Because this differs per operating system,
you have to create this file based on the template (tools/ant/properties/packaging.tmpl) which
is set for a likely linux environment.  
+   The build will attempt to use a file called `tools/ant/properties/packaging.properties`
to carry out checksum (md5)and signing (pgp) tasks. Because this differs per operating system,
you have to create this file based on the template (`tools/ant/properties/packaging.tmpl`)
which is set for a likely linux environment.  
  
    Most Unix distributions come with either md5 or md5sum. An md5sum utility for Windows
can be downloaded as a part of the !GnuWin32 port of the core Gnu utilities, from: http://gnuwin32.sourceforge.net/packages/coreutils.htm.
A standalone md5 utility can be found at http://www.fourmilab.ch/md5/. Note, for the executable
available from this last location, the correct option for output is md5 -n.
  
@@ -195, +193 @@

  
    GPG is available for a variety of platforms from http://gnupg.org. PGP is a commercial
product which is available from http://pgp.com.
  
-   Your KEY needs to be in the KEYS file in trunk, KEYS file on the branch if you've created
one, and the KEYS file in /www/www.apache.org/dist/db/derby at people.apache.org.
+   Your KEY needs to be in the KEYS file in trunk, KEYS file on the branch if you've created
one, and the KEYS file in `/www/www.apache.org/dist/db/derby` at people.apache.org.
   
-   You need to make sure the tools/ant/properties/packaging.properties file has correct information
for your pgp tool.
+   You need to make sure the `tools/ant/properties/packaging.properties` file has correct
information for your pgp tool.
  
   1. Ensure you have appropriate jdks available
  
@@ -209, +207 @@

  
   1. Check out a clean copy of the doc tree
  
-   Once you have a copy of the documentation on your local machine, you will need to update
the property ${docs.out} in tools/ant/properties/packaging.properties to point to your local
copy of the documentation. 
+   Once you have a copy of the documentation on your local machine, you will need to update
the property ${docs.out} in `tools/ant/properties/packaging.properties` to point to your local
copy of the documentation. 
  
    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.
  
@@ -228, +226 @@

  === For each release candidate ===
  
  Verify that:
-  * `beta` property is false. If this is the first release candidate off this branch the
`beta` property should have been set to false in a [#FirstRC previous section].  If this is
an update relase, the `beta` property should have been set to false as a part of the release
cycle for the first release off this branch. 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. 
+  * `beta` property is false. If this is the first release candidate off this branch the
`beta` property should have been set to false in a [#FirstRC previous section].  If this is
an update relase, the `beta` property should have been set to false as a part of the release
cycle for the first release off this branch. 
   * Version number is correct. For the first release candidate off a branch, the version
number should have been set immediately [#BranchVersion after cutting the branch]. For subsequent
release candidates, including update release candidates, the version number should have been
bumped after [#Bump4th spinning the previous release candidate]
  
+ The third and fourth parts of the version number are combined into a single property, maint,
where maint = (third digit * 1000000) + fourth digit. 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. 
+ 
  ==== Check-ins just before generating release artifacts ====
  
  /!\ '''Check in the new version number after RC is spun?''' 
@@ -240, +240 @@

   1. Generate `RELEASE_NOTES.html` in the branch and check it into the svn repository. Please
consult the instructions for [http://wiki.apache.org/db-derby/ReleaseNoteProcess generating
release notes].
  
   1. ( /!\ ''Deprecated for versions >= 10.3'') Finalize CHANGES. This can include items
in addition to the RELEASE_NOTES, which are purely for user purposes. 
-   The tool java/tools/ChangesFileGenerator.java can help you generate this file; it works
similar to the ReleaseNotesGenerater.
+   The tool `java/tools/ChangesFileGenerator.java` can help you generate this file; it works
similar to the !ReleaseNotesGenerator.
  
   1. Check in the latest SQLState documentation.
  
@@ -256, +256 @@

  	- doc tree
  	  - with DITA library
  	  - with latest SQLState
- 	- `KEYS` checked in
+ 	- KEYS checked in
+ 
- 	- `RELEASE_NOTES` and CHANGES(''not for 10.3 and higher'') checked in
+ 	- RELEASE_NOTES and CHANGES (''only for version < 10.3'') checked in
+ 
- 	- `md5` & `pgp` and docs info set correctly in `tools/ant/properties/packaging.properties`
and available (PATH)
+ 	- md5 & pgp and docs info set correctly in `tools/ant/properties/packaging.properties`
and available (PATH)
+ 
  	- generated updated `tools/release/maintversion.properties` ( /!\ ''' Is it still required?''')
+ 
- 	- `ant.properties` set correctly for:
+ 	- `ant.properties` set correctly for: jdk15, jdk16, jsr169
- 		osgi.jar(10.3 and earlier), jdk15, jdk16, jsr169
+ 
  	- sane not set in ant.properties /!\ ''' Is this still true?'''
+ 
  	- non-source files for building source available: `junit.jar`, `felix.jar`, (with 10.3
and earlier: `osgi.jar`), dita library (again).
   
   1. Build the documentation.
@@ -340, +345 @@

  
    The md5 checksums can be verified by generating them via another method. For example,
using openssl:
  
-   openssl md5 < db-derby-10.1.1.0-src.zip
+    {{{openssl md5 < db-derby-10.1.1.0-src.zip
+ }}}
  
-   And comparing the output of openssl to the output from ant in db-derby-10.1.1.0-src.zip.md5
+   And comparing the output of openssl to the output from ant in `db-derby-10.1.1.0-src.zip.md5`
  
- Keep the jars/insane/*.jar files available. You will need them for maven deployment after
the vote is complete.
+   Keep the `jars/insane/*.jar` files available. You will need them for maven deployment
after the vote is complete.
  
   1. [[Anchor(Bump4th)]]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}}}
+   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties
tools/release/maintversion.properties
-   The third and fourth parts of the version are combined into a single property, maint,
where maint = (third digit * 1000000) + fourth digit. 
+ }}}
+ 
+   /!\ '''Is this still necessary?'''
+ 
+   {{{cd tools/release
+ ant bumplastdigit}}}
+ 
+   /!\ '''Commit the changed version number here?'''
+   
   
   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.
+   Copy the files from `tools/release` to your `public_html` directory on people.apache.org.
If you are not building the Eclipse plugin yourself, you must also copy `snapshot/derby_core_plugin*.*`
to `public_html` so that it is available to anyone wanting to build the Eclipse plugin. Post
to derby-dev so that others can begin testing.
  
   1. Vote on the distributions
  
-   Call for a vote on derby-dev to have the distributions posted on your public_html accepted
for the release. A vote needs to be running for at least 7 days, so, give at least that much
time before closing the vote to give adequate time for others to inspect and test the distributions.
If no-one has responded after a week, prod gently until you get a response. A majority of
votes, and at least one binding +1 vote are required for acceptance.
+   Call for a vote on derby-dev to have the distributions posted on your `public_html` accepted
for the release. A vote needs to be running for at least 7 days, so, give at least that much
time before closing the vote to give adequate time for others to inspect and test the distributions.
If no-one has responded after a week, prod gently until you get a response. A majority of
votes, and at least one binding +1 vote are required for acceptance.
  
    Forward or bcc a copy of the call for vote to private@db.apache.org so the DB PMC is aware
that a vote is in progress. Also forward the results post to private@db.apache.org. (Note:
do not '''cc''' the PMC; '''bcc''' or forward a copy of the post.)
  

Mime
View raw message