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, 30 Apr 2008 10:56:26 -0000
Message-ID: <20080430105626.20895.32143@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

------------------------------------------------------------------------------
    * The JSR169 support
  
   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.
  
-   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.  
+   {X} 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.
+   {i} 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.
- 
-   For pgp look on below...
  
   1. Make sure your public PGP/GPG key is in the KEYS file, and preferably after it has been signed.
- 
-   For information about PGP and why it is used to sign release binaries at Apache, please read [http://people.apache.org/~henkp/trust/].
+   {i} For information about PGP and why it is used to sign release binaries at Apache, please read [http://people.apache.org/~henkp/trust/].
  
-   You should create a PGP key for yourself if you do not have one, and upload it to at least one, preferably two, of the main public keyservers, e.g. pgp.mit.edu. You will need this key to sign the release binaries. Your key should be tied into the Apache web of trust, which means you should have at least one person sign your key, and you should have done `gpg --refresh-keys` to get that person's signature before you follow the steps at the top of the KEYS file.
+   You should create a PGP key for yourself if you do not have one, and upload it to at least one, preferably two, of the main public keyservers, e.g. `pgp.mit.edu`. You will need this key to sign the release binaries. Your key should be tied into the Apache web of trust, which means you should have at least one person sign your key, and you should have done `gpg --refresh-keys` to get that person's signature before you follow the steps at the top of the `KEYS` file.
  
-   GPG is available for a variety of platforms from http://gnupg.org. PGP is a commercial product which is available from http://pgp.com.
+   {i} 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.
+   {X} 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
  
-   See BUILDING.txt for information on JSR169 and OSGI support.
+   {i} See: `BUILDING.txt` for information on JSR169 and OSGI support.
  
    For 10.2 forward, make sure that you have JDK 1.6 available and that you've set the jdk16 property to the JAVA_HOME for your JDK 1.6 installation in your ant.properties so that the JDBC 4.0 classes are built and the JDBC 4.0 javadoc is created.
  
@@ -228, +226 @@

  
    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.
+   To build the documentation, you need to obtain `DITA-OT1.1.2.1_bin-ASL.zip` and place it in the docs' tree lib. 
  
+   {i} See: [http://db.apache.org/derby/manuals/dita.html] for more info about building the documentation.
+ 
-  1. (Optional:) Have eclipse installed or make arrangements with someone willing to build the eclipse ui plugin. As release manager you need to have access to the plugin zips if you don't build them yourself (e.g. the volunteer can attach the plugin zips to a Jira issue).
+  1. (Optional:) Have eclipse installed or make arrangements with someone willing to build the eclipse ui plugin. As release manager you need to have access to the plugin zips if you don't build them yourself (e.g. the volunteer can attach the plugin zips to a Jira issue). <!> If you are not building the plugin yourself, make sure that the ''beta'' status of the plugin matches that of the release candidate you are building.
  
  [[Anchor(FirstRC)]]
  === For the first release candidate on a new branch ===