Author: mfranklin
Date: Tue Apr 3 02:05:01 2012
New Revision: 1308652
URL: http://svn.apache.org/viewvc?rev=1308652&view=rev
Log:
Updated release documentation for SvnPubSub
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=1308652&r1=1308651&r2=1308652&view=diff
==============================================================================
--- rave/site/trunk/content/release-process.mdtext (original)
+++ rave/site/trunk/content/release-process.mdtext Tue Apr 3 02:05:01 2012
@@ -136,7 +136,7 @@ All of the steps below apply to both the
* reply to the initial email and prepend to the original subject
"[RESULT]"
* Include a list of everyone who voted +1, 0 or -1.
-13. Finalizing a release
+12. Finalizing a release
1. Promote the staged nexus artifacts
@@ -145,29 +145,47 @@ All of the steps below apply to both the
* Staging tab --> Name column --> org.apache.rave
* Right click on the closed staging repo (org.apache.rave-XXX) and
select Release.
- 3. Copy the distribution artifacts over to the distribution area (for
rave-project only)
-
- * $ ssh ${user.name}@people.apache.org
- * $ mkdir /www/www.apache.org/dist/rave/${project.version}
- * $ cd /www/www.apache.org/dist/rave/${project.version}
- * $ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-project-${project.version}-source-release.zip
- * $ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-project-${project.version}-source-release.zip.asc
- * $ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-project-${project.version}-source-release.zip.md5
- * $ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-project/${project.version}/rave-project-${project.version}-source-release.zip.sha1
- * $ cp -rfv /www/people.apache.org/builds/rave/${project.version}/* ./
- * $ rm -rfv /www/people.apache.org/builds/rave/${project.version}
- * Make sure all the copied files have g+rw set and only o+r set
+ 2. Copy the source artifacts over to the distribution area
- $ find . -user ${user.name} -type f | xargs chmod 664
- $ find . -user ${user.name} -type d | xargs chmod 775
-
- 4. Publish the staged website
+ * $ svn co
https://dist.apache.org/repos/dist/release/incubator/rave/sources
./rave-sources (KEEP this directory until after the release process has been
completed)
+ * $ cd ./rave-sources
+ * $ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/${project.name}/${project.version}/${project.name}-${project.version}-source-release.zip
+ * $ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/${project.name}/${project.version}/${project.name}-${project.version}-source-release.zip.asc
+ * $ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/${project.name}/${project.version}/${project.name}-${project.version}-source-release.zip.md5
+ * $ wget
https://repository.apache.org/content/repositories/releases/org/apache/rave/${project.name}/${project.version}/${project.name}-${project.version}-source-release.zip.sha1
+ * $ svn add ${project.name}-*
+ * $ svn commit -m "Committing Source Release for
${project.name}-${project.version}
+
+ 3. Copy the binary artifacts over to the distribution area (for
rave-project only)
+
+ * $ svn co
https://dist.apache.org/repos/dist/release/incubator/rave/binaries
./rave-binaries (KEEP this directory until after the release process has been
completed)
+ * $ cd rave-binaries
+ * $ scp
people.apache.org:/www/people.apache.org/builds/incubator/rave/${project.version}/*
./
+ * $ svn add *
+ * $ svn commit -m "Committing Binary Release for
${project.name}-${project.version}
+
+ 4. Update the staged website
+
+ * Update the downloads page to add new version using the mirrored URLs
+ * Modify the URL for the prior release to the archived URL for the
release
+
+ 5. Publish the website
+
+ * WAIT 24hrs after committing releases for mirrors to replicate
+ * Publish updates to the download page
+
+ 6. Delete the prior versions
+
+ * Navigate to the release directories checked out in the prior steps
+ * Delete the prior release artifacts using the svn delete command
+ * Commit the deletion
14. Update the JIRA versions page to close all issues, mark the version as
"released", and set the date to the date that the release was approved. You may
also need to make a new release entry for the next release.
+
15. Announcing the release
- 1. After the mirrors have had time to update (24 hours to be on the safe
side) update the wiki with pointers to the new release
- 2. Make a news announcement on the Rave homepage.
- 3. Make an announcement about the release on the [email protected],
[email protected], and [email protected] list as per the Apache
Announcement Mailing Lists page)
+
+ * Make a news announcement on the Rave homepage.
+ * Make an announcement about the release on the [email protected],
[email protected], and [email protected] list as per the Apache
Announcement Mailing Lists page)
####Recovering from a vetoed release
@@ -218,5 +236,4 @@ In order to perform a combined release o
* Build the rave-master FIRST
* When prompted to change the rave-project dependency on rave-master
SNAPSHOT, do so to the release that you just built
* Execute the remaining steps using the following e-mail templates
- * [PMC Release Vote](PPMC_Combined.txt)
-
+ * [PMC Release Vote](PPMC_Combined.txt)
\ No newline at end of file
