You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-commits@db.apache.org by mb...@apache.org on 2015/03/20 22:25:08 UTC
svn commit: r1668154 - /db/jdo/HowToReleaseJDO.html
Author: mbo
Date: Fri Mar 20 21:25:08 2015
New Revision: 1668154
URL: http://svn.apache.org/r1668154
Log:
Update HowToReleaseJDO based on experience when releasing JDO 3.1
Modified:
db/jdo/HowToReleaseJDO.html
Modified: db/jdo/HowToReleaseJDO.html
URL: http://svn.apache.org/viewvc/db/jdo/HowToReleaseJDO.html?rev=1668154&r1=1668153&r2=1668154&view=diff
==============================================================================
--- db/jdo/HowToReleaseJDO.html (original)
+++ db/jdo/HowToReleaseJDO.html Fri Mar 20 21:25:08 2015
@@ -75,6 +75,9 @@
<h2>Detailed process steps</h2>
<p> </p>
<ol>
+ <li>You might want to run <a href="http://creadur.apache.org/rat">Apache Rat</a>
+ to check the sources for any lisence issues.
+ <pre>mvn apache-rat:check</pre>
<li>Create a branch from the trunk and increment the spec or major
number. For example, create a 3.1 branch from the trunk.
<pre>cd jdo
@@ -98,7 +101,6 @@ https://svn.apache.org/repos/asf/db/jdo/
the tck pom.xml.</li>
<li>If needed, apply patches from the trunk or branches to the new
branch.</li>
- <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:
@@ -107,10 +109,13 @@ https://svn.apache.org/repos/asf/db/jdo/
<dd>File names and version references in the Overview section
(for a major release only.)
</dd>
- <dt>trunk/tck/RunRules.html </dt>
+ <dt>branches/<i>version</i>/tck/RunRules.html </dt>
<dd>Update version number</dd>
</dl>
</li>
+ <li>Check the scm settings in the pom.xml files in the new branch and
+ make sure they refer the new branch (instead of the trunk).
+ </li>
<li>Follow the instructions at <a href="http://www.apache.org/dev/publishing-maven-artifacts.html">
Publishing Maven Artifacts</a> to set up your development environment.
</li>
@@ -124,13 +129,15 @@ https://svn.apache.org/repos/asf/db/jdo/
</pre>
This creates the .jar and .pom files
in the target directory of each subproject.
+ Be prepared to enter your key passcode when prompted. This happens multiple times.
</li>
- <li>Run RAT, which is at <a href="http://creadur.apache.org/rat/">
- http://creadur.apache.org/rat/</a>, on the release. </li>
+ <li>Run <a href="http://creadur.apache.org/rat">Apache Rat</a> on the release. </li>
</li>
<li>
Do a dry run prepare and deployment of a snapshot release.
- Be prepared to enter your key passcode when prompted.
+ You might want to do this in a fresh workspace, since you cannot have local modifications
+ when preparing a release. The files in lib/ext and lib/jdori count as local modifications.
+ Be prepared to enter your key passcode when prompted. This happens multiple times.
<pre>
mvn release:prepare -Papache-release -DautoVersionSubmodules=true -DdryRun=true -Dresume=false
@@ -144,7 +151,8 @@ https://svn.apache.org/repos/asf/db/jdo/
<pre>
mvn release:clean -Papache-release
mvn release:prepare -Papache-release
- </pre>
+ </pre>
+ Note: If you're located in Europe then release:prepare may fail with 'Unable to tag SCM' and ' svn: No such revision X '. Wait 10 seconds and run mvn release:prepare again.
</li>
<li>
Stage the release for a vote.
@@ -152,10 +160,11 @@ mvn release:prepare -Papache-release
mvn release:perform -Papache-release
</pre>
</li>
- <li>Close the Staged Repository
- See <a href="https://docs.sonatype.org/display/Repository/Closing+a+Staging+Repository"
- >Closing a Staging Repository</a> for details on connecting to the Nexus UI.
- The Nexus repository URL is https://repository.apache.org/index.html.
+ <li>Go to <a href="https://repository.apache.org/index.html">the Nexus repository</a>,
+ login with your apache account, click on Staging Repositories in the menu on the left
+ and close the staged repository. Press the refresh button to see the new status 'closed'.
+ See <a href="http://books.sonatype.com/nexus-book/reference/staging-repositories.html">
+ 11.4.1. Closing an Open Repository</a> for details.
</li>
<li>Send an announcement to test the release to the
jdo-dev@db.apache.org alias. If problems are found, fix and
@@ -167,8 +176,10 @@ mvn release:perform -Papache-release
vote to jdo-dev@db.apache.org, cc: general@db.apache.org, and
include [VOTE] [RESULTS] in the subject line.</li>
<li>After testing and voting is complete,
- follow the instructions at <a href="https://docs.sonatype.org/display/Repository/Releasing+a+Staging+Repository">
- Releasing a Staging Repository</a> to release the artifacts.
+ follow the instructions at
+ <a href="http://books.sonatype.com/nexus-book/reference/staging-repositories.html">
+ 11.4.3. Releasing a Staging Repository</a>
+ to release the artifacts.
</li>
<li>Update the distribution repository at http://apache.org/dist/db/jdo/
by adding the new release directory to the svnpubsub directory.
@@ -207,7 +218,7 @@ mvn release:perform -Papache-release
Note that the cgi page will not be active until it is on the
server, so can't really be tested.</li>
<li>Add the new files to the subversion repository.
- <pre>svn add site/src/site/xdoc/releases/release-<i>N.n</i>.html
+ <pre>svn add site/src/site/xdoc/releases/release-<i>N.n</i>.xml
svn add site/docs/releases/release-<i>N.n</i>.html
svn add site/src/site/resources/releases/release-<i>N.n</i>.cgi
svn add site/docs/releases/release-<i>N.n</i>.cgi