Author: mfranklin
Date: Mon Apr 2 21:10:57 2012
New Revision: 1308571
URL: http://svn.apache.org/viewvc?rev=1308571&view=rev
Log:
Removed references to incubator and updated with correct wording for TLP
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=1308571&r1=1308570&r2=1308571&view=diff
==============================================================================
--- rave/site/trunk/content/release-process.mdtext (original)
+++ rave/site/trunk/content/release-process.mdtext Mon Apr 2 21:10:57 2012
@@ -16,7 +16,7 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-###Incubator Release Steps Overview
+###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.
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))
@@ -35,7 +35,7 @@ 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. Also, transition any Resolved
issues to the Closed state.
+ 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.
@@ -57,7 +57,7 @@ All of the steps below apply to both the
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}-incubating
+ * SCM release tag - *DO NOT TAKE THE DEFAULT* - ${project.version}
* New development version - take the default
* GPG Passprhase
@@ -87,7 +87,7 @@ All of the steps below apply to both the
9. Perform the release
* This step will create a maven staging repository and site for use in
testing and voting.
- $ mvn release:perform -Papache-release -Duser.name=<your_apache_uid>
+ $ mvn release:perform -Papache-release
* *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.*
@@ -111,39 +111,31 @@ All of the steps below apply to both the
* 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
+ * $ gpg -ab ./rave-portal/target/rave-*${project.version}*.bin.zip
+ * $ gpg -ab ./rave-portal/target/rave-*${project.version}*.bin.tar.gz
+ * $ gpg --print-md SHA512 rave-*${project.version}*.bin.zip >
rave-*${project.version}*.bin.zip.sha
+ * $ gpg --print-md SHA512 rave-*${project.version}*.bin.tar.gz >
rave-*${project.version}*.bin.zip.sha
+ * $ gpg --print-md MD5 rave-*${project.version}*.bin.zip >
rave-*${project.version}*.bin.zip.md5
+ * $ gpg --print-md MD5 rave-*${project.version}*.bin.tar.gz >
rave-*${project.version}*.bin.zip.md5
2. Copy the artifacts to the staging area
- * $ ssh people.apache.org mkdir
/www/people.apache.org/builds/incubator/rave/0.1-incubating
- * $ scp
./rave-portal/target/rave-*${project.version}*-incubating.bin.*
${user.name}@people.apache.org:/www/people.apache.org/builds/incubator/rave/${project.version}/
- * Verify they are downloadable from
http://people.apache.org/builds/incubator/rave/0.1-incubating/
+ * $ ssh people.apache.org mkdir
/www/people.apache.org/builds/rave/${project.version}
+ * $ scp ./rave-portal/target/rave-*${project.version}*.bin.*
${user.name}@people.apache.org:/www/people.apache.org/builds/rave/${project.version}/
+ * Verify they are downloadable from
http://people.apache.org/builds/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)
+ 1. Create a VOTE email thread on dev@ to record votes as replies, like
[this](release-vote.txt)
+ 2. Create a DISCUSS email thread on 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://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
5. After the vote has been open for at least 72 hours, has at least three
+1 PMC votes and no -1 votes, then post the results to the vote thread by -
- * reply to the initial email and prepend to the original subject
"[RESULTS]"
+ * reply to the initial email and prepend to the original subject
"[RESULT]"
* Include a list of everyone who voted +1, 0 or -1.
-12. Put the release candidate up for an Incubator PMC vote
- 1. Create a VOTE email thread on general@incubator to record votes as
replies, like [this](vote-ipmc.txt)
-
- 2. After the vote has been open for at least 72 hours, has at least three
+1 Incubator PMC votes and no -1 votes, then post the results to the vote
thread by -
- * replying to the initial email and prepend to the original subject
"[RESULTS]"
- * Include a list of everyone who voted +1, 0 or -1.
-
13. Finalizing a release
1. Promote the staged nexus artifacts
@@ -156,14 +148,14 @@ All of the steps below apply to both the
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/incubator/rave/${project.version}
- * $ cd /www/www.apache.org/dist/incubator/rave/${project.version}
+ * $ 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/incubator/rave/${project.version}/* ./
- * $ rm -rfv
/www/people.apache.org/builds/incubator/rave/${project.version}
+ * $ 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
$ find . -user ${user.name} -type f | xargs chmod 664
@@ -171,11 +163,11 @@ All of the steps below apply to both the
4. Publish the staged website
-14. Update the JIRA versions page to 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.
+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],
[email protected], and [email protected] list as per the Apache
Announcement Mailing Lists page)
+ 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)
####Recovering from a vetoed release
@@ -186,11 +178,11 @@ All of the steps below apply to both the
3. Delete the svn tag created by the release:perform step -
- $ svn del https://svn.apache.org/repos/asf/rave/tags/0.1-incubating -m
"deleting tag from rolled back release"
+ $ svn del https://svn.apache.org/repos/asf/rave/tags/${project.version}
-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}
+ * $ rm -rfv /www/people.apache.org/builds/rave/${project.version}
+ * $ rm -rfv /www/www.apache.org/dist/rave/${project.version}
4. Drop the nexus staging repo
1. https://repository.apache.org/index.html
@@ -226,7 +218,5 @@ 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
- * [PPMC Release Vote](PPMC_Combined.txt)
- * [IMPC Release Vote](IPMC_Combined.txt)
-
+ * [PMC Release Vote](PPMC_Combined.txt)
