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 Wed, 30 Apr 2008 11:48:57 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. 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. For versions < 10.3; finalize `CHANGES`. For later releases the CHANGES file has
been superseded by `CHANGES.html` This can include items in addition to the RELEASE_NOTES,
which are purely for user purposes. 
+  1. For versions < 10.3; finalize `CHANGES`. For later releases the `CHANGES` file has
been superseded by `CHANGES.html` 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 can
be invoked by running `ant genchanges` in `tools/release`.
+   {i} The tool `java/tools/ChangesFileGenerator.java` can help you generate this file. It
can be invoked by running `ant genchanges` in `tools/release`.
  
-  1. Check in the latest SQLState documentation. (This step can be done in advance, but make
sure that no !SQLState has been modified before creating the release). 
+  1. Check in the latest SQLState documentation. (This step can be done in advance, but make
sure that no SQLState has been modified before creating the release). 
  
    Build the source tree. The SQLStates are documented in the Reference Guide on the following
page: `rrefexcept71493.dita`. This file is generated by the Derby build and placed in `classes/doc`.
Take the version of this file generated by building the code branch and check it into the
doc branch at `src/ref/rrefexcept71493.dita`.
  
@@ -271, +272 @@

  	- doc tree
  	  - with DITA library
  	  - with latest SQLState
- 	- KEYS checked in
+ 	- `KEYS` checked in
  
- 	- RELEASE_NOTES and CHANGES (''only for version < 10.3'') checked in
+ 	- `RELEASE_NOTES.html` and CHANGES (''only for version < 10.3'') checked in. <!>
`CHANGES.html` (''version 10.3 and later'') should ''not'' be checked in.
  
  	- md5 & pgp and docs info set correctly in `tools/ant/properties/packaging.properties`
and available (PATH)
  
  	- `ant.properties` set correctly for: jdk15, jdk16, jsr169
  
- 	- sane not set in ant.properties
+ 	- sane not set in `ant.properties`
  
  	- 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.
  
-   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]. 
+   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.
+ 
+   {i} Information on building the docs is located at [http://db.apache.org/derby/manuals/dita.html].

  
   1. [[Anchor(CreateDistros)]]Create the distributions for release by running:
  
@@ -303, +306 @@

  ant release
  ant sign}}}
  
-   You will need to enter your PGP passphrase several times as the release distributions
are signed. (''Note that you can save yourself some typing by using gpg's `--pasphrase-fd
<fd>` option. This instructs gpg to read the passphrase from the specified file descriptor'').
+   You will need to enter your PGP passphrase several times as the release distributions
are signed. 
+ 
+   (!) You can save yourself some typing by using gpg's `--passphrase-fd <fd>` option.
This instructs gpg to read the passphrase from the specified file descriptor.
  
    This will create the following files in your tools/release directory:
  
@@ -318, +323 @@

  
    The Eclipse core plugin is generated in the snapshot directory at the top level by the
snapshot target. You should also create the Eclipse UI plugins (see `plugins/eclipse/readme.txt`,
except use the core plugin created in the snapshot directory), but this requires Eclipse.
If you don't want to do it yourself, those interested in the Eclipse plugins will likely volunteer
to generate them for you. 
  
-   /!\ Note that ui-plugin can be built as a ''beta''. If you don't build the ui-plugin yourself,
make sure that its ''beta'' status matches that of the release candidate you are building.

+   <!> Note that ui-plugin can be built as a ''beta''. If you don't build the ui-plugin
yourself, make sure that its ''beta'' status matches that of the release candidate you are
building. 
  
    You should also create checksums and signatures for these files with:
  
@@ -327, +332 @@

  md5 -q derby_ui_plugin_[version].zip > derby_ui_plugin_[version].zip.md5
  md5 -q derby_core_plugin_[version].zip > derby_core_plugin_[version].zip.md5}}}
  
-   [[Anchor(SignOne)]]There is a problem with the `ant sign` target on Cygwin that may occur
elsewhere. If for some reason the Ant 'sign' target hangs, it may be prompting and waiting
for input that you cannot see. In that case, you can also use this simple script to automate
signing the release archives:
+   [[Anchor(SignOne)]] {X} There is a problem with the `ant sign` target on Cygwin that may
occur elsewhere. If for some reason the `ant sign` target hangs, it may be prompting and waiting
for input that you cannot see. 
+ 
+   (!) In that case, you can also use this simple script to automate signing the release
archives:
  
    {{{#!/bin/sh signone() {
    gpg --detach-sign --armor $1
@@ -345, +352 @@

  
    Invoking this 'sign.sh db-derby-10.1.1.0' would sign all of the release archives for Derby
10.1.1.0, for example. 
  
-   Be sure to replace the commands for gpg and md5 with the correct commands for your system.
Note that on cygwin, the md5 switch is "-n" rather than "-q".
+   {X} Be sure to replace the commands for gpg and md5 with the correct commands for your
system. Note that on cygwin, the md5 switch is "-n" rather than "-q".
  
   1. Verify the signatures and checksums.
  
-   As an example, the Derby 10.1 archives would be verified with PGP as follows:
+   As an example, the Derby 10.1 archives would be verified with GPG as follows:
  
    {{{gpg --verify derby_ui_plugin_1.1.0.zip.asc derby_ui_plugin_1.1.0.zip
  gpg --verify derby_core_plugin_10.1.1.zip.asc derby_core_plugin_10.1.1.zip
@@ -364, +371 @@

  
    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`
  
-   Keep the `jars/insane/*.jar` files available. You will need them for maven deployment
after the vote is complete.
+  1. Keep the `jars/insane/*.jar` files available. You will need them for maven deployment
after the vote is complete.
+   (!) It is advisable to copy the jars to another directory and include the version number
of the release candidate in the directory name. This way you avoid having to extract the jars
from the release artifacts if you inadvertently overwrite the jars (through a rebuild) before
deploying to the maven repository.
  
   1. [[Anchor(Bump4th)]]Bump the fourth digit of the source in preparation for a possible
next build:
  

Mime
View raw message