jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From resc...@apache.org
Subject svn commit: r1857340 - /jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Date Thu, 11 Apr 2019 14:24:26 GMT
Author: reschke
Date: Thu Apr 11 14:24:26 2019
New Revision: 1857340

URL: http://svn.apache.org/viewvc?rev=1857340&view=rev
Log:
add a check for stable Oak referencing unstable Jackrabbit

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=1857340&r1=1857339&r2=1857340&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Thu Apr 11 14:24:26 2019
@@ -85,10 +85,14 @@ Release management tasks
         -@Version("1.5.0")
         +@Version("1.6.0")
 8. If this is a release with Java 7 or older, make sure that your `MAVEN_OPTS` contain `-Dhttps.protocols=TLSv1.2`.
-9. Build and deploy the release artifacts with Maven. See [below](#Steps_to_build_the_release_artifacts)
for the exact steps.
-10. 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).
-11. Close the staged repository, giving it a meaningful name, such as "Apache Jackrabbit
2.x.y RC"
-12. Upload the artifacts to https://dist.apache.org/repos/dist/dev/jackrabbit/ as follows:
+9. When doing "stable" release (even-numbered), check that we do not have
+   dependencies to unstable releases. In particular, stable releases of Oak
+   should not reference unstable Jackrabbit releases (if this is the case,
+   a new stable Jackrabbit release might be required in order to proceed).
+10. Build and deploy the release artifacts with Maven. See [below](#Steps_to_build_the_release_artifacts)
for the exact steps.
+11. 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).
+12. Close the staged repository, giving it a meaningful name, such as "Apache Jackrabbit
2.x.y RC"
+13. Upload the artifacts to https://dist.apache.org/repos/dist/dev/jackrabbit/ as follows:
 
         # TARGET - where https://dist.apache.org/repos/dist/dev/jackrabbit/ is checked out
         # SOURCE - where the release was built
@@ -107,11 +111,11 @@ Release management tasks
         svn add oak/$version
         svn commit -m "Apache Jackrabbit Oak $version release candidate" oak/$version
 
-13. Find the vote template (`./target/checkout/target/vote.txt`) generated by the Maven build
and follow the instructions to verify the build yourself
-14. Start the vote thread by emailing the applicable mailing list ([Jackrabbit](mailto:dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20x.y.z),
[Oak](mailto:oak-dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20Oak%20x.y.z))
-15. Mark the version as released in Jira: [Jackrabbit Jira](https://issues.apache.org/jira/plugins/servlet/project-config/JCR/versions),
+14. Find the vote template (`./target/checkout/target/vote.txt`) generated by the Maven build
and follow the instructions to verify the build yourself
+15. Start the vote thread by emailing the applicable mailing list ([Jackrabbit](mailto:dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20x.y.z),
[Oak](mailto:oak-dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20Oak%20x.y.z))
+16. Mark the version as released in Jira: [Jackrabbit Jira](https://issues.apache.org/jira/plugins/servlet/project-config/JCR/versions),
    [Oak Jira](https://issues.apache.org/jira/plugins/servlet/project-config/OAK/versions).
You'll see all the defined project versions. From the settings menu, choose 'Release' on the
version.
-16. Wait 72 hours (we usually allow three business days, so be careful when a weekend is
ahead)
+17. Wait 72 hours (we usually allow three business days, so be careful when a weekend is
ahead)
 
 ### Part II: after the release vote
    



Mime
View raw message