jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dav...@apache.org
Subject svn commit: r1760538 - /jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Date Tue, 13 Sep 2016 13:13:54 GMT
Author: davide
Date: Tue Sep 13 13:13:54 2016
New Revision: 1760538

URL: http://svn.apache.org/viewvc?rev=1760538&view=rev
Log:
minor release process update


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=1760538&r1=1760537&r2=1760538&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Tue Sep 13 13:13:54 2016
@@ -53,26 +53,26 @@ See [Appendix B](#Appendix_B:_Maven_sett
 Release management tasks
 ------------------------
 1. Make sure that an appropriate version for the release is entered in Jira and that 
-    all the related issues have been resolved. This is also a good time to create a 
-    new version in JIRA for the next release.
-2. Create a `RELEASE-NOTES.txt` file in the root folder of the project to be released. 
+    all the related issues have been resolved. 
+2. Create a new version in JIRA for the next release.
+3. Create a `RELEASE-NOTES.txt` file in the root folder of the project to be released. 
     If such a file already exists, update it for the release. See a previous 
     release notes for examples of what to include. The release note report in Jira is a 
     useful source of required information: Open the [Jira Oak](https://issues.apache.org/jira/browse/OAK)
page, 
     click on the release, then on the "Release Notes" button on the top right. When done,
commit the file.
-3. Build and deploy the release artifacts with Maven. See below for the exact steps.
-4. Close the [staged repository](https://repository.apache.org/index.html#stagingRepositories)
on repository.apache.org.
-5. Upload the artifacts to https://dist.apache.org/repos/dist/dev/jackrabbit/ (instructions
at the end of the build)
+4. Build and deploy the release artifacts with Maven. See below for the exact steps.
+5. Close the [staged repository](https://repository.apache.org/index.html#stagingRepositories)
on repository.apache.org.
+6. Upload the artifacts to https://dist.apache.org/repos/dist/dev/jackrabbit/ (instructions
at the end of the build)
 
         cd /path/to/jackrabbit-dev
         scp -r /path/to/jackrabbit/target/checkout/target/$version $version
         svn add $version
         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. 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
+7. Start the vote thread, wait 72 hours. See the vote template generated by the Maven build.
+8. 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.
+9. If the vote fails (easy case first) remove the tag from svn, drop the staged repository
and revert the version release in Jira- done
+10. 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),
 
@@ -83,10 +83,10 @@ Release management tasks
     * 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!
 
-10. Update the Jackrabbit web site to point to the new release.
+11. Update the Jackrabbit web site to point to the new release.
     1. index.md
     2. downloads.md (while doing so please a) remove obsoleted entries, and b) move new entries
for Jackrabbit and/or Oak to the top)
-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.
+12. 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



Mime
View raw message