You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by am...@apache.org on 2015/11/25 10:42:31 UTC

svn commit: r1716341 - /jackrabbit/site/trunk/src/site/markdown/creating-releases.md

Author: amitj
Date: Wed Nov 25 09:42:30 2015
New Revision: 1716341

URL: http://svn.apache.org/viewvc?rev=1716341&view=rev
Log:
Moved Jira release step to when the RC is put up/start of voting

Modified:
    jackrabbit/site/trunk/src/site/markdown/creating-releases.md

Modified: jackrabbit/site/trunk/src/site/markdown/creating-releases.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/creating-releases.md?rev=1716341&r1=1716340&r2=1716341&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Wed Nov 25 09:42:30 2015
@@ -70,23 +70,23 @@ Release management tasks
         svn commit -m "Apache Jackrabbit $version release candidate" $version
 
 6. Start the vote thread, wait 72 hours. See the vote template generated by the Maven build.
-7. If the vote fails (easy case first) remove the tag from svn and drop the staged repository - done
-8. If the vote is successful
-    1. close the vote by publishing the results
-    2. copy the release candidate from dev/jackrabbit to release/jackrabbit in https://dist.apache.org/repos/dist/, and delete any older releases from the same branch (they're automatically archived),
+7. Mark the version as released in Jira: [Jira Project Home](https://issues.apache.org/jira/browse/JCR) -> Project Summary -> Administer Project. Under Versions, click <More>. You'll see all the defined project versions. From the settings menu, choose 'Release' on the version.
+8. If the vote fails (easy case first) remove the tag from svn, drop the staged repository and revert the version release in Jira- done
+9. If the vote is successful
+    * close the vote by publishing the results
+    * copy the release candidate from dev/jackrabbit to release/jackrabbit in https://dist.apache.org/repos/dist/, and delete any older releases from the same branch (they're automatically archived),
 
         svn move -m "Apache Jackrabbit $version" \
         https://dist.apache.org/repos/dist/dev/jackrabbit/$version \
         https://dist.apache.org/repos/dist/release/jackrabbit/$version
 
-    3. release the [staged repository](https://repository.apache.org/index.html#stagingRepositories) for synchronization to Maven central.
-    4. mark the version as released in Jira: [Jira Project Home](https://issues.apache.org/jira/browse/JCR) -> Project Summary -> Administer Project. Under Versions, click <More>. You'll see all the defined project versions. From the settings menu, choose 'Release' on the version.
-    5. close all the issues included in the release: Jira Project Home -> Change Log -> Choose the released version. From the issue list you have the option to bulk update all of the included issues. Just 'Transition Issues' from 'Resolved' to 'Closed' and you are done!
+    * release the [staged repository](https://repository.apache.org/index.html#stagingRepositories) for synchronization to Maven central.
+    * close all the issues included in the release: Jira Project Home -> Change Log -> Choose the released version. From the issue list you have the option to bulk update all of the included issues. Just 'Transition Issues' from 'Resolved' to 'Closed' and you are done!
 
-9. Update the Jackrabbit web site to point to the new release.
+10. Update the Jackrabbit web site to point to the new release.
     1. index.md
     2. downloads.md
-10. Send the release announcement once the web site and download mirrors have been synced. Please note the announce mails needs to be sent from an @apache.org address.
+11. Send the release announcement once the web site and download mirrors have been synced. Please note the announce mails needs to be sent from an @apache.org address.
 
 
 Steps to build the release artifacts