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 Fri, 21 Oct 2005 02:08:06 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

------------------------------------------------------------------------------
  
   1. Bump the third version number 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
+ 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).  
+ 
   1. Create the release distributions and checksums, sign the distributions
  
-   Once the bug list hits zero, 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:
+   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:
  
    {{{svn up
  ant clobber
@@ -136, +146 @@

  
    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.   
+ 
+   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.
+ 
-  1. Put distributions onto mirrors
+  1. If the vote passes, put distributions onto mirrors
  
    First, read:
  
@@ -171, +185 @@

  
    Include a description of the project, and a description of any significant new features
or important bug fixes. Every tech news blog remotely related to Java or databases will pick
up the announcement and post it verbatim, so it's a good idea to spell check it, proofread
it a couple of times, and/or get input from other committers on its content.
  
+  1. Tag the release in subversion.
+ 
+   {{{svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/{trunk_or_branchname}/
https://svn.apache.org/repos/asf/db/derby/tags/{version}/}}}
+ 
+  1. For major releases, create a new branch for the release.
+ 
+   {{{svn copy -r {rev} https://svn.apache.org/repos/asf/db/derby/trunk/ https://svn.apache.org/repos/asf/db/derby/branches/{branchname}/}}}
+ 
   1. Bump the version number to next version.
  
    For a bugfix release, follow steps 4 and 5 in the snapshot section. There is not currently
a target for bumping the version number for a feature release. You should edit release.properties
by hand, and then, from the top, run:
@@ -179, +201 @@

  cd tools/release
  ant regex.masters}}}
  
-   Don't forget to post to derby-dev requesting that a new version be added to JIRA for the
next version of Derby.
+   Don't forget to post to derby-dev requesting that a new version be added to JIRA for the
next version of Derby. If the release was a feature release and you're bumping the version
on the release to the next major or minor version, don't forget to set the beta flag back
to true.
  
   1. Update STATUS again.
  

Mime
View raw message