db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mcai...@apache.org
Subject svn commit: r686280 - /db/jdo/HowToReleaseJDO.html
Date Fri, 15 Aug 2008 17:02:02 GMT
Author: mcaisse
Date: Fri Aug 15 10:02:02 2008
New Revision: 686280

URL: http://svn.apache.org/viewvc?rev=686280&view=rev
JDO-585 Add step to process for updating release notes for a bug fix release


Modified: db/jdo/HowToReleaseJDO.html
URL: http://svn.apache.org/viewvc/db/jdo/HowToReleaseJDO.html?rev=686280&r1=686279&r2=686280&view=diff
--- db/jdo/HowToReleaseJDO.html (original)
+++ db/jdo/HowToReleaseJDO.html Fri Aug 15 10:02:02 2008
@@ -25,6 +25,7 @@
     <LI><a href="#procoverview">Overview of the process</a></LI>
     <LI><a href="#procdetail">Detailed process steps</a></LI>
     <LI><a href="#site">Site updates</a></LI>
+    <LI><a href="#next">Preparation for the next release</a></LI>
     <LI><a href="#postrelease">Post release modifications and documentation</a></LI>
 <h1>How to Release an Apache JDO Distribution</h1>
@@ -123,6 +124,19 @@
 If needed, update the dependency to JPOX in the tck20 project.xml.
 If needed, apply patches from the trunk or branches to the new branch.
+<a name="version"></a>
+<LI>Update version numbers where necessary in projects to be released,
+if these changes haven't been made previously.
+Check the following files:
+    <DT>trunk/project.properties
+    <DD>Change value of currentVersion
+    <DT>trunk/README.html
+    <DD>File names and version references in the Overview section
+    <DT>trunk/JDO20.MF, api2/API2.MF, api2-legacy/API2.MF
+    <DD>Update Specification-Version and Bundle-Version
 <LI>Copy the JNDI implementation jars (providerutil.jar and fscontext.jar) 
 to the branch lib/ext directory. This is needed to test the tck before 
 distributing it.
@@ -202,6 +216,9 @@
 svn commit "JDO-XXX create release 2.n" releases/2.n
+If the release is a bug fix release to a maintenance release, update README.txt in the parent
branch, adding the following line: "This release has been deprecated. Please use version 2.x.y.",
with a link to the svn web interface for that version. 
 <LI>After updating the site (below), announce the release to the Apache community via
email to 
@@ -241,6 +258,8 @@
 <LI> Follow the instructions in site/HOWTO to push the site changes to the Apache web
+<a name="next"></a><h2>Preparation for the next release</h2>
+In trunk, update version numbers for the next spec or major release. See the instruction
under <a href="#version">Detailed process steps</a>.
 <a name="postrelease"></a>
 <h2>Post release modifications and documentation</h2>
 Follow this procedure if a significant bug is found or if the TCK must be modified because
a test challenge is found to be valid.

View raw message