Author: jasha
Date: Wed Apr 4 16:22:49 2012
New Revision: 1309480
URL: http://svn.apache.org/viewvc?rev=1309480&view=rev
Log:
Update release instructions
- add option for autoVersionSubmodules (saves a lot of typing)
- mention snapshot dependencies
- instruction for userid
Modified:
rave/site/trunk/content/release-process.mdtext
Modified: rave/site/trunk/content/release-process.mdtext
URL:
http://svn.apache.org/viewvc/rave/site/trunk/content/release-process.mdtext?rev=1309480&r1=1309479&r2=1309480&view=diff
==============================================================================
--- rave/site/trunk/content/release-process.mdtext (original)
+++ rave/site/trunk/content/release-process.mdtext Wed Apr 4 16:22:49 2012
@@ -35,11 +35,11 @@ All of the steps below apply to both the
4. Make sure the [Release Setup](release-setup.html) steps have been
performed.
2. Prepare the source for release:
- 1. Cleanup JIRA so the Fix Version in issues resolved since the last
release includes this release version correctly.
+ 1. Cleanup JIRA so the Fix Version in issues resolved since the last
release includes this release version correctly.
2. Update the text files in a working copy of the project root -
1. Update the CHANGELOG based on the Text release reports from JIRA.
2. Review and update README.txt if needed.
- 3. Commit any changes back to svn
+ 3. Commit any changes back to svn
3. Stage any Roadmap or Release landing pages on the site.
3. Checkout a clean copy of the trunk to release using command line svn.
@@ -52,16 +52,18 @@ All of the steps below apply to both the
5. Do a dry run of the release:prepare step:
- $ mvn -P apache-release release:prepare -DdryRun=true
+ $ mvn -P apache-release release:prepare -DautoVersionSubmodules=true
-DdryRun=true
- The dry run will not commit any changes back to SVN and gives you the
opportunity to verify that the release process will complete as expected. You
will be prompted for the following information :
+ The dry run will not commit any changes back to SVN and gives you the
opportunity to verify that the release process will complete as expected. You
will be prompted for the following information :
* Release version - take the default
* SCM release tag - *DO NOT TAKE THE DEFAULT* - ${project.version}
* New development version - take the default
* GPG Passprhase
- *If you cancel a release:prepare before it updates the pom.xml versions,
then use the release:clean goal to just remove the extra files that were
created.*
+ *If you cancel a release:prepare before it updates the pom.xml versions,
then use the release:clean goal to just remove the extra files that were
created.*
+
+ The Maven release plugin checks for SNAPSHOT dependencies in pom's. It
will not complete the prepare goal until all SNAPSHOT dependencies are resolved.
6. Verify that the release process completed as expected
1. The release plugin will create pom.xml.tag files which contain the
changes that would have been committed to SVN. The only differences between
pom.xml.tag and it's corresponding pom.xml file should be the version number.
@@ -80,7 +82,7 @@ All of the steps below apply to both the
1. Run the "release:prepare" step for real this time. You'll be prompted
for the same version information.
- $ mvn -P apache-release release:prepare
+ $ mvn -P apache-release release:prepare -DautoVersionSubmodules=true
2. Backup (zip or tar) your local release candidate directory in case you
need to rollback the release after the next step is performed.
@@ -91,6 +93,8 @@ All of the steps below apply to both the
* *If your local OS userid doesn't match your Apache userid, then you'll
have to also override the value provided by the OS to Maven for the site-deploy
step to work. This is known to work for Linux, but not for Mac and unknown for
Windows.*
+ -Duser.name=[your_apache_uid]
+
10. Verify the Nexus release artifacts
1. Verify the HTML links in site are correct
