jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From resc...@apache.org
Subject svn commit: r1772836 - /jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Date Tue, 06 Dec 2016 07:21:02 GMT
Author: reschke
Date: Tue Dec  6 07:21:02 2016
New Revision: 1772836

URL: http://svn.apache.org/viewvc?rev=1772836&view=rev
Log:
restructure list to make closing the staged repo more prominent

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=1772836&r1=1772835&r2=1772836&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Tue Dec  6 07:21:02 2016
@@ -61,18 +61,19 @@ Release management tasks
     useful source of required information: Open the [JCR Jira](https://issues.apache.org/jira/browse/JCR)
or [OAK Jira](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.
 4. Build and deploy the release artifacts with Maven. See below for the exact steps.
-5. Do a sanity check that the [staged repository](https://repository.apache.org/index.html#stagingRepositories)
on repository.apache.org contains all artifacts (19 projects for Jackrabbit), then close it.
-6. Upload the artifacts to https://dist.apache.org/repos/dist/dev/jackrabbit/ (instructions
at the end of the build)
+5. Do a sanity check that the [staged repository](https://repository.apache.org/index.html#stagingRepositories)
on repository.apache.org contains all artifacts (~19 projects for Jackrabbit).
+6. Close the staged repository, giving it a meaningful name, such as "Apache Jackrabbit 2.x.y
RC"
+7. 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
 
-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
+8. Start the vote thread, wait 72 hours. See the vote template generated by the Maven build.
+9. 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.
+10. If the vote fails (easy case first) remove the tag from svn, drop the staged repository
and revert the version release in Jira- done
+11. 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/
-- **be careful to properly set the version variable!!!**
 
@@ -84,11 +85,11 @@ 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!
 
-11. Update the Jackrabbit web site to point to the new release.
+12. 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)
-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.
-13. If the release was a Jackrabbit release used in Oak, make sure to also update the dependency
in oak-parent/pom.xml (example: [OAK-4743](https://issues.apache.org/jira/browse/OAK-4743)
- the current mapping is Jackrabbit 2.13 -> Oak trunk, Jackrabbit 2.12 -> Oak 1.4 and
1.2, Jackrabbit 2.8 -> Oak 1.0)
+13. 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.
+14. If the release was a Jackrabbit release used in Oak, make sure to also update the dependency
in oak-parent/pom.xml (example: [OAK-4743](https://issues.apache.org/jira/browse/OAK-4743)
- the current mapping is Jackrabbit 2.13 -> Oak trunk, Jackrabbit 2.12 -> Oak 1.4 and
1.2, Jackrabbit 2.8 -> Oak 1.0)
 
 
 Steps to build the release artifacts



Mime
View raw message