You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rave.apache.org by mf...@apache.org on 2011/06/15 23:55:44 UTC
svn commit: r1136215 -
/incubator/rave/site/trunk/content/rave/release-process.mdtext
Author: mfranklin
Date: Wed Jun 15 21:55:43 2011
New Revision: 1136215
URL: http://svn.apache.org/viewvc?rev=1136215&view=rev
Log:
Fixed formatting errors (Supports RAVE-46)
Modified:
incubator/rave/site/trunk/content/rave/release-process.mdtext
Modified: incubator/rave/site/trunk/content/rave/release-process.mdtext
URL: http://svn.apache.org/viewvc/incubator/rave/site/trunk/content/rave/release-process.mdtext?rev=1136215&r1=1136214&r2=1136215&view=diff
==============================================================================
--- incubator/rave/site/trunk/content/rave/release-process.mdtext (original)
+++ incubator/rave/site/trunk/content/rave/release-process.mdtext Wed Jun 15 21:55:43 2011
@@ -22,32 +22,33 @@ Notice: Licensed to the Apache Softwa
1. Increase the default Java heap available to Maven (required for Java SE 6)
export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"
-
2. Use the latest Sun 1.6.0 JDK
3. Use Maven 3.0.3 or later
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. Also, transition any Resolved issues to the Closed state.
- 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. Stage any Roadmap or Release landing pages on the site.
+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. Also, transition any Resolved issues to the Closed state.
+ 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. Stage any Roadmap or Release landing pages on the site.
3. Checkout a clean copy of the trunk to release using command line svn.
*Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws off the rat:check processing.*
-4. Use `mvn verify` to verify the source has the required headers before trying to release.
-5. Do a dry run of the release:prepare step.
+
+4. Use `mvn -P pedantic verify` to verify the source has the required headers before trying to release.
+
+5. Do a dry run of the release:prepare step:
+
+ $ mvn -Papache-release release:prepare -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 :
* Release version - take the default
* SCM release tag - *DO NOT TAKE THE DEFAULT* -: : 0.1-incubating
- * New development version - take the default
- * GPG Passprhase
-
- $ mvn -Papache-release release:prepare -DdryRun=true
+ * 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.*
@@ -56,20 +57,17 @@ Notice: Licensed to the Apache Softwa
2. If other formatting changes have been made you should review the changes and then commit them -
$ svn commit -m "fixing formatting for release"
-
3. Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.
- 4. verify signatures ([Verifying release signatures](http://incubator.apache.org/rave/cwiki/release-process.html#ReleaseProcess-Verifyingreleasesignatures))
+ 4. Verify signatures ([Verifying release signatures](http://incubator.apache.org/rave/release-process.html#verify_signatures))
-7. Once any failures or required updates have been committed to svn, rollback the release prepare files -
+7. Once any failures or required updates have been committed to svn, rollback the release prepare files:
$ mvn -Papache-release release:rollback
8. Prepare the release
1. Run the "release:prepare" step for real this time. You'll be prompted for the same version information.
- *Different arguments and steps are required as there are problems with the maven-jar-plugin and maven-release-plugin when using the test-jar goal. See http://jira.codehaus.org/browse/MJAR-68 and http://jira.codehaus.org/browse/MRELEASE-285.*
-
- $ mvn release:prepare -Papache-release -DpreparationGoals="clean install cargo:package"
+ $ mvn release:prepare -Papache-release -DpreparationGoals="clean install cargo:package"
2. Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.
@@ -98,7 +96,7 @@ Notice: Licensed to the Apache Softwa
2. Create a DISCUSS email thread on rave-dev@ for any vote questions, [this](release-discuss.txt)
3. Perform a review of the release and cast your vote. See the following for more details on Apache releases
- [http://www.apache.org/dev/release.html](http://www.apache.org/dev/release.html)
+ [http://www.apache.org/dev/release.html](http://www.apache.org/dev/release.html)
[http://incubator.apache.org/guides/releasemanagement.html](http://incubator.apache.org/guides/releasemanagement.html)
4. A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. See - Recovering from a vetoed release
@@ -128,18 +126,18 @@ Notice: Licensed to the Apache Softwa
2. Copy the distribution artifacts over to the distribution area
- $ ssh ${user.name}@people.apache.org
- $ mkdir /www/www.apache.org/dist/incubator/rave/${project.version}
- $ cd /www/www.apache.org/dist/incubator/rave/${project.version}
- $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip
- $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.asc
- $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.md5
- $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.sha1
+ $ ssh ${user.name}@people.apache.org
+ $ mkdir /www/www.apache.org/dist/incubator/rave/${project.version}
+ $ cd /www/www.apache.org/dist/incubator/rave/${project.version}
+ $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip
+ $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.asc
+ $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.md5
+ $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.sha1
**Make sure all the copied files have g+rw set and only o+r set**
- $ find . -user ${user.name} -type f | xargs chmod 664
- $ find . -user ${user.name} -type d | xargs chmod 775
+ $ find . -user ${user.name} -type f | xargs chmod 664
+ $ find . -user ${user.name} -type d | xargs chmod 775
*Note: All of the artifacts are in the maven repos, but we may create an assembly to publish in future releases*