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/29 18:17:06 UTC
svn commit: r1141144 -
/incubator/rave/site/trunk/content/rave/release-process.mdtext
Author: mfranklin
Date: Wed Jun 29 16:17:06 2011
New Revision: 1141144
URL: http://svn.apache.org/viewvc?rev=1141144&view=rev
Log:
Fixed incorrect handling of demo artifacts
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=1141144&r1=1141143&r2=1141144&view=diff
==============================================================================
--- incubator/rave/site/trunk/content/rave/release-process.mdtext (original)
+++ incubator/rave/site/trunk/content/rave/release-process.mdtext Wed Jun 29 16:17:06 2011
@@ -19,7 +19,7 @@ Notice: Licensed to the Apache Softwa
###Incubator Release Steps Overview
There are two distinct sets of artifacts that are released on independent schedules: rave-master & rave-project. The rave-master is the project metadata (committers, roles, etc) and only needs to be released when there is a change in the structure of the project itself (committers, mentors, etc). The rave-project artifacts are comprised of all rave source code, binaries and a standalone demo.
-The following steps are performed for each of the rave-project and rave-master releases separately.
+All of the steps below apply to both the master and project releases, unless otherwise specified. As an alternative to releasing separately, the projects MAY be released together as one combined release. The steps for this can be found below. ([Combined Release Steps](#combined))
####Common Release Steps
@@ -89,7 +89,7 @@ The following steps are performed for ea
* *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.*
-10. Verify the release artifacts
+10. Verify the Nexus release artifacts
1. Verify the HTML links in site are correct
@@ -103,6 +103,23 @@ The following steps are performed for ea
* Staging tab --> Name column --> org.apache.rave
* Right click on the open staging repo (org.apache.rave-XXX) and select Close.
+11. Build and stage the Demo artifacts (Rave Project releases Only)
+
+ 1. Build and sign the standalone demo:
+
+ * Checkout the tag from SVN
+ * $ mvn -P dist
+ * $ gpg -ab ./rave-portal/target/rave-*${project.version}*-incubating.bin.zip
+ * $ gpg -ab ./rave-portal/target/rave-*${project.version}*-incubating.bin.tar.gz
+ * $ gpg --print-md SHA512 rave-*${project.version}*-incubating.bin.zip > rave-*${project.version}*-incubating.bin.zip.sha
+ * $ gpg --print-md SHA512 rave-*${project.version}*-incubating.bin.tar.gz > rave-*${project.version}*-incubating.bin.zip.sha
+ * $ gpg --print-md MD5 rave-*${project.version}*-incubating.bin.zip > rave-*${project.version}*-incubating.bin.zip.md5
+ * $ gpg --print-md MD5 rave-*${project.version}*-incubating.bin.tar.gz > rave-*${project.version}*-incubating.bin.zip.md5
+
+ 2. Copy the artifacts to the staging area
+
+ * $ scp ./rave-portal/target/rave-*${project.version}*-incubating.bin.* ${user.name}@people.apache.org:/www/people.apache.org/builds/incubator/rave/${project.version}/
+
11. Put the release candidate up for a vote
1. Create a VOTE email thread on rave-dev@ to record votes as replies, like [this](release-vote.txt)
2. Create a DISCUSS email thread on rave-dev@ for any vote questions, [this](release-discuss.txt)
@@ -132,17 +149,6 @@ The following steps are performed for ea
* Staging tab --> Name column --> org.apache.rave
* Right click on the closed staging repo (org.apache.rave-XXX) and select Promote.
- 2. Build and sign the standalone demo (for rave-project releases only):
-
- * Checkout the tag from SVN
- * $ mvn -P dist
- * $ gpg -ab ./rave-portal/target/rave-*${project.version}*-incubating.bin.zip
- * $ gpg -ab ./rave-portal/target/rave-*${project.version}*-incubating.bin.tar.gz
- * $ gpg --print-md SHA512 rave-*${project.version}*-incubating.bin.zip > rave-*${project.version}*-incubating.bin.zip.sha
- * $ gpg --print-md SHA512 rave-*${project.version}*-incubating.bin.tar.gz > rave-*${project.version}*-incubating.bin.zip.sha
- * $ gpg --print-md MD5 rave-*${project.version}*-incubating.bin.zip > rave-*${project.version}*-incubating.bin.zip.md5
- * $ gpg --print-md MD5 rave-*${project.version}*-incubating.bin.tar.gz > rave-*${project.version}*-incubating.bin.zip.md5
-
3. Copy the distribution artifacts over to the distribution area (for rave-project only)
* $ ssh ${user.name}@people.apache.org
@@ -152,13 +158,12 @@ The following steps are performed for ea
* $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-parent-${project.version}-source-release.zip.asc
* $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-parent-${project.version}-source-release.zip.md5
* $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-parent-${project.version}-source-release.zip.sha1
+ * $ cp -rfv /www/people.apache.org/builds/incubator/rave/${project.version}/* ./
+ * $ rm -rfv /www/people.apache.org/builds/incubator/rave/${project.version}
* 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
-
- * $ exit
- * $ scp ./rave-portal/target/rave-*${project.version}*-incubating.bin.* ${user.name}@people.apache.org:/www/www.apache.org/dist/incubator/rave/${project.version}/
4. Publish the staged website
@@ -175,27 +180,23 @@ The following steps are performed for ea
[CANCELED]
-2. Rollback the version upgrades in trunk by either -
- 1. Restore the 0.1-rc1.tar.gz and run
-
- $ mvn -Papache-release release:rollback
-
- 2. Manually revert the versions in trunk to the prior version and commit
-
3. Delete the svn tag created by the release:perform step -
$ svn del https://svn.apache.org/repos/asf/incubator/rave/tags/0.1-incubating -m "deleting tag from rolled back release"
+4. Delete the build artifacts on people & www
+ * $ rm -rfv /www/people.apache.org/builds/incubator/rave/${project.version}
+ * $ rm -rfv /www/www.apache.org/dist/incubator/rave/${project.version}
+
4. Drop the nexus staging repo
1. https://repository.apache.org/index.html
2. Enterprise --> Staging
3. Staging tab --> Name column --> org.apache.rave
4. Right click on the closed staging repo (org.apache.rave-XXX) and select Drop.
-5. Remote the staged site
+5. Remove the staged site
-6. Make the required updates that caused the vote to be canceled
-7. Spin another release candidate!
+6. Make the required updates that caused the vote to be canceled during the next release cycle
<a name="verify_signatures" />
####Verifying release signatures
@@ -210,3 +211,16 @@ You'll need to look at the output to ens
gpg: Good signature from ...
gpg: Signature made ...
+
+
+<a name="combined" />
+####Combined Release
+
+In order to perform a combined release of the rave-master and rave-project trunks, do the following:
+
+ * Perform Steps 1-9 of the [release](#release-steps) for Rave Master & Rave Project
+ * Do NOT perform step 10 until steps 1-9 have been completed for BOTH projects
+ * Execute the remaining steps using the following e-mail templates
+ * [PPMC Release Vote](PPMC_Combined.txt)
+
+