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 AndrewMcIntyre
Date Tue, 25 Oct 2005 18:35:26 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 AndrewMcIntyre:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
  
    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. Ideally, your key should be tied into the Apache web of trust.
  
-  1. Bump the third version number and check in the new version and test masters
+  1. Bump the third version number, finalize CHANGES, and check in the new version and test
masters
  
    There is not currently an ant target for bumping the third version number. 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
remove the beta flag at this time. You should update tools/ant/properties/release.properties
by hand and then run:
  
-   {{{java maintversion2props tools/ant/properties/release.properties tools/release/maintversion.properties
+   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties
tools/release/maintversion.properties}}}
- cd tools/release
+   {{{cd tools/release
  ant regex.masters}}}
  
    TODO: the regex.masters target does not currently account for changes in the beta flag.
  
-   Check in the updated properties files and masters. 'svn up' in your subversion view to
bring all files in your view up to the latest revision. Otherwise, the version output by svn
which is captured for the build number will be a range (e.g. 290275:320938).  
+   Finalize any comments added to CHANGES, so that you do not need to alter the file before
you are ready to build. Check in the updated files. 'svn up' in your subversion view to bring
all files in your view up to the latest revision. Otherwise, the version output by svn which
is captured for the build number will be a range (e.g. 290275:320938).  
  
   1. Build the documentation, or grab a copy from the website.
  
    The documentation needs to be included in the -bin distribution, so you will need a copy
of the documentation ready when running the ant release target. Information on building the
docs is located at [http://db.apache.org/derby/manuals/dita.html]. Another option is to log
in to minotaur.apache.org and grab the current uploaded copy on the website, in /www/db.apache.org/derby/docs/.
Tar up the correct version of the docs into your home directory (don't leave a big tarfile
in /www/db.apache.org/derby/docs please!) and download it to your local machine with sftp.
Untar it to a local directory, that is not inside your subversion view where you are building
the release or it will be included in the -src distribution built by the release target.
  
+  1. Copy packaging.tmpl to packaging.properties in tools/release and modify as necessary.
+ 
-   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. Check that the settings in tools/ant/properties/packaging.properties
are correct for your md5 hash tool and pgp/gpg tool and then
  
   1. Create the release distributions and checksums, sign the distributions
  
-   Once the bug list hits zero and the version, create the distributions for release. Check
that the settings in tools/ant/properties/packaging.properties are correct for your md5 hash
tool and pgp/gpg tool and then run:
+   Check your classpath for osgi.jar for OSGI support and make sure jsr169compile.classpath
is set for J2ME support. If you have the sane property set in your ant.propertie, remove it
at this time to prevent it from overriding the false setting passed into the snapshot target.
Create the distributions for release by running:
  
    {{{svn up
  ant clobber
@@ -112, +114 @@

  cd tools/release
  ant release}}}
  
-   You will need to enter your PGP passphrase several times as the release distributions
are signed. This will create the following files in your tools/release directory:
+     You will need to enter your PGP passphrase several times as the release distributions
are signed. This will create the following files in your tools/release directory:
  
    *db-derby-[version]-bin.tar.gz
    *db-derby-[version]-bin.zip
@@ -125, +127 @@

  
    {{{gpg --armor --detach-sign derby_ui_plugin_[version].zip
  gpg --armor --detach-sign derby_core_plugin_[version].zip
- md5 -q derby_ui_plugin_[version].zip > derby_ui_plugin_[version].md5
+ md5 -q derby_ui_plugin_[version].zip > derby_ui_plugin_[version].zip.md5
- md5 -q derby_core_plugin_[version].zip > derby_core_plugin_[version].md5}}}
+ md5 -q derby_core_plugin_[version].zip > derby_core_plugin_[version].zip.md5}}}
+ 
+   TODO: Add information about signing manually if the Ant sign target has trouble.
   
   1. Verify the signatures and checksums.
  
@@ -147, +151 @@

  
    And comparing the output of openssl to the output from ant in db-derby-10.1.1.0-src.zip.md5
  
+  1. Bump the fourth digit of the version
+ 
+   See step #4 in the snapshot section.
+ 
   1. Post the distributions
  
    Copy the files from tools/release to your public_html directory on minotaur.apache.org.
Post to derby-dev so that others can begin testing.
@@ -155, +163 @@

  
    Call for a vote on derby-dev to have the distributions posted on your public_html accepted
for the release. It is a good idea to wait at least a week 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.
  
-  1. If vote does not pass and go back to 'Drive bug list to zero', and bump fourth version
digit.   
+  1. If vote does not pass and go back to 'Drive bug list to zero'.   
  
-   If the vote does not pass and additional release candidates need to be made, the fourth
digit should be bumped as described in the Snapshot section. Presumably, it won't have passed
because of a showstopper-type bug or similar issue, so go back to the bug-fixing section.
+   If the vote does not pass and additional release candidates need to be made, then presumably
it won't have passed because of a showstopper-type bug or similar issue. So, go back to the
bug-fixing section.
  
   1. If the vote passes, put distributions onto mirrors
  
@@ -230, +238 @@

  
    For a bugfix release, follow the instructions in sections 4 and 5 of the Snapshot section
to bump the fourth digit. There is not currently a target for bumping the version number for
a feature release. You should edit release.properties by hand to bump the major/minor properties
as appropriate, zero out the maint property, and set the beta flag back to true. Then, from
the top, run:
  
-   {{{java maintversion2props tools/ant/properties/release.properties tools/release/maintversion.properties
+   {{{java org.apache.derbyBuild.maintversion2props tools/ant/properties/release.properties
tools/release/maintversion.properties}}}
- cd tools/release
+   {{{cd tools/release
  ant regex.masters}}}
  
    See #6 for caveat concerning the beta flag. Don't forget to post to derby-dev requesting
that a new version be added to JIRA for the next version of Derby.

Mime
View raw message