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

[re...@apache.org]

Author: reschke
Date: Wed Nov 16 10:38:12 2022
New Revision: 1905337

URL: http://svn.apache.org/viewvc?rev=1905337&view=rev
Log:
add instruction to also check with highest supposed-to-be-supported Guava version

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=1905337&r1=1905336&r2=1905337&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Wed Nov 16 10:38:12 2022
@@ -92,18 +92,22 @@ Release management tasks
         +@Version("1.6.0")
 11. On the other hand, if this is a release from trunk, carefully review all
     export versions and check that no change introduces new dependencies on
-    Guava (see [OAK-7182](https://issues.apache.org/jira/browse/OAK-7182))
-12. If this is a release with Java 7 or older, make sure that your `MAVEN_OPTS` contain `-Dhttps.protocols=TLSv1.2`.
-13. When doing "stable" release (even-numbered), check that we do not have
+    Guava (see [OAK-7182](https://issues.apache.org/jira/browse/OAK-7182)).
+12. For Oak releases that support a range of Guava versions (right now trunk and
+    1.22), make sure the system builds and tests with the highest version in the range
+    as well (see `guava.osgi.import` property in `oak-parent/pom.xml`) - right now that is 20.0.
+    Use `-Dguava.version=...` for the tests.
+13. If this is a release with Java 7 or older, make sure that your `MAVEN_OPTS` contain `-Dhttps.protocols=TLSv1.2`.
+14. 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).
-14. Build and deploy the release artifacts with Maven. See [below](#Steps_to_build_the_release_artifacts) for the exact steps.
-15. Mark the version as released in Jira: [Jackrabbit Jira](https://issues.apache.org/jira/plugins/servlet/project-config/JCR/versions),
+15. Build and deploy the release artifacts with Maven. See [below](#Steps_to_build_the_release_artifacts) for the exact steps.
+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. 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).
-17. Close the staged repository, giving it a meaningful name, such as "Apache Jackrabbit 2.x.y RC"
-18. Upload the artifacts to https://dist.apache.org/repos/dist/dev/jackrabbit/ as follows:
+17. 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).
+18. Close the staged repository, giving it a meaningful name, such as "Apache Jackrabbit 2.x.y RC"
+19. 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
@@ -122,9 +126,9 @@ Release management tasks
         svn add oak/$version
         svn commit -m "Apache Jackrabbit Oak $version release candidate" oak/$version
 
-19. Find the vote template (`./target/checkout/target/vote.txt`) generated by the Maven build and follow the instructions to verify the build yourself
-20. 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))
-21. Wait 72 hours (we usually allow three business days, so be careful when a weekend is ahead)
+20. Find the vote template (`./target/checkout/target/vote.txt`) generated by the Maven build and follow the instructions to verify the build yourself
+21. 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))
+22. Wait 72 hours (we usually allow three business days, so be careful when a weekend is ahead)
 
 ### Part II: after the release vote