Mailing-List: contact jdo-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r638577 - /db/jdo/HowToReleaseJDO.txt
Date: Tue, 18 Mar 2008 21:17:54 -0000
To: jdo-commits@db.apache.org
From: mcaisse@apache.org
Message-Id: <20080318211754.3C91D1A983A@eris.apache.org>

Author: mcaisse
Date: Tue Mar 18 14:17:53 2008
New Revision: 638577

URL: http://svn.apache.org/viewvc?rev=638577&view=rev
Log:
Various small additions and corrections for the 2.1 release

Modified:
    db/jdo/HowToReleaseJDO.txt

Modified: db/jdo/HowToReleaseJDO.txt
URL: http://svn.apache.org/viewvc/db/jdo/HowToReleaseJDO.txt?rev=638577&r1=638576&r2=638577&view=diff
==============================================================================
--- db/jdo/HowToReleaseJDO.txt (original)
+++ db/jdo/HowToReleaseJDO.txt Tue Mar 18 14:17:53 2008
@@ -60,9 +60,10 @@
 Detailed process steps:
 
 1. Create a branch from the trunk or from another branch. If you are 
-creating a major release, e.g. 2.0, create a 2.0 branch from the
-trunk. If creating an update release, e.g. 2.0.1.3, create a branch from
-the 2.0.1 or 2.0.1.2 branch and apply updates to it.
+creating a major or spec maintenance release, e.g. 2.0, 2.1,
+create a 2.n branch from the trunk. If creating an bug-fix release,
+e.g. 2.0.1.3, create a branch from the 2.0.1 or 2.0.1.2
+branch and apply updates to it.
 
 cd jdo
 svn copy https://svn.apache.org/repos/asf/db/jdo/trunk \
@@ -70,7 +71,7 @@
 
 2. Remove the projects and files that are not being released.
 
-pushd branches/2.0
+pushd branches/2.n
 svn rm api11 btree fostore20 query20 runtime20 ri11 tck11 JDO11.MF 
 svn commit -m "Remove projects and files that are not being released"
 
@@ -87,37 +88,44 @@
 to the branch lib/ext directory. This is needed to test the tck before 
 distributing it.
 
-cp trunk/lib/ext/* branches/2.0/lib/ext
+cp trunk/lib/ext/* branches/2.n/lib/ext
 
 5. Build the distribution. This creates .gz files and .zip files in the 
 target/distributions directory of each project. It also creates the .jar
 and .pom files.  It then copies the release artifacts to the 
-releases/2.0/dist directory. The dist directory is in a format that
+releases/2.n/dist directory. The dist directory is in a format that
 can be copied directly to the apache dist directory for distribution.
 
 Note: Failure possibly due to insufficient heap space was fixed by setting
 the environment variable MAVEN_OPTS="-Xmx1024m -Xms1024m -XX:MaxPermSize=512m"
 
-pushd branches/2.0
+pushd branches/2.n
+maven tck2.default
 maven tck2.dist
 popd
 
 6. Test the release in the branch.
 
-pushd branches/2.0/tck20
+pushd branches/2.n/tck20
 maven installSchema
 maven runtck.jdori
 popd
 
+Also run RAT on the release: http://code.google.com/p/arat/
+
 7. Sign the artifacts. You must have a gpg key in order to perform this step.
 The sign-directory script is checked into jdo/bin. Edit this script to refer
 to your own environment (do not check it in).
 
-bin/sign-directory releases/2.0/dist
+bin/sign-directory releases/2.n/dist/jdo2.<n>-rc<m>
 
 8. Push the artifacts to the staging area on the apache server.
 
-scp -r releases/2.0/dist people.apache.org:~/public_html
+scp -r releases/2.n/dist <username>@people.apache.org:~/public_html
+
+Make sure that all the directories have executable permission:
+
+chmod a+x <dir>
 
 9. Test the release from the staging area. Send an announcement to vote
 on the release to the jdo-dev@db.apache.org alias.  The message subject
@@ -134,21 +142,21 @@
 
 11. Check the distribution into svn
 
-svn add releases/2.0
-svn commit "JDO-XXX create release 2.0" releases/2.0
+svn add releases/2.n
+svn commit "JDO-XXX create release 2.n" releases/2.n
 
 12. Update the JDO web site to point the downloads page to the release.
-In site/xdocs/releases create release-2.0.html.  In site/docs/releases create
-release-2.0.cgi.  The .cgi file contents are identical to the other .cgi
+In site/xdocs/releases create release-2.n.html.  In site/docs/releases create
+release-2.n.cgi.  The .cgi file contents are identical to the other .cgi
 files in the release directory; only the file name differs.  Edit 
 site/xdocs/downloads.xml to link to the new release page .cgi document.
 Set the svn properties svn:eol-style to native and svn:executable to true 
 for the .cgi files. Build the site from the site directory:
 
 ant
-svn add xdocs/releases/release-2.0.html 
-svn add docs/releases/release-2.0.html 
-svn add docs/releases/release-2.0.cgi 
+svn add xdocs/releases/release-2.n.html 
+svn add docs/releases/release-2.n.html 
+svn add docs/releases/release-2.n.cgi 
 svn commit
 
 Follow the instructions in HOWTO to push the site changes to