You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by re...@apache.org on 2018/02/05 08:59:03 UTC
svn commit: r1823139 -
/jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Author: reschke
Date: Mon Feb 5 08:59:03 2018
New Revision: 1823139
URL: http://svn.apache.org/viewvc?rev=1823139&view=rev
Log:
add note about testing Oak with the new Jackrabbit 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=1823139&r1=1823138&r2=1823139&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Mon Feb 5 08:59:03 2018
@@ -56,7 +56,7 @@ Release management tasks
### Part I: up to the release vote
-1. When releasing from trunk, consider checking the CVE database for vulnerabilities in dependencies,
+1. Consider checking the CVE database for vulnerabilities in dependencies,
using `mvn org.owasp:dependency-check-maven:3.0.2:aggregate` (first run will be slow because CVE
databases are downloaded and parsed). If dependencies need action, open tickets and make sure they
are marked as candidate backports where applicable.
@@ -74,10 +74,14 @@ Release management tasks
Double-check that all version numbers in the updated Release Notes are accurate.
When done, commit the file.
5. If the branch is one that requires Java 8 or newer, make sure that the API docs can indeed be built with Java 8, using both `javadoc:javadoc` and `javadoc:jar`.
-6. Build and deploy the release artifacts with Maven. See [below](#Steps_to_build_the_release_artifacts) for the exact steps.
-7. 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).
-8. Close the staged repository, giving it a meaningful name, such as "Apache Jackrabbit 2.x.y RC"
-9. Upload the artifacts to https://dist.apache.org/repos/dist/dev/jackrabbit/ (instructions at the end of the build)
+6. When releasing a Jackrabbit version that will be used in Oak, make sure it
+ doesn't break Oak.
+ * Check by building the applicable Oak version using `mvn clean install -PintegrationTesting -Djackrabbit.version=2.x.y-SNAPSHOT`
+ * If the update does require changes in Oak, open JIRA tickets and link them to the JIRA tickets tracking the release activity.
+7. Build and deploy the release artifacts with Maven. See [below](#Steps_to_build_the_release_artifacts) for the exact steps.
+8. 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).
+9. Close the staged repository, giving it a meaningful name, such as "Apache Jackrabbit 2.x.y RC"
+10. Upload the artifacts to https://dist.apache.org/repos/dist/dev/jackrabbit/ (instructions at the end of the build)
# TARGET - where https://dist.apache.org/repos/dist/dev/jackrabbit/ is checked out
# SOURCE - where the release was built
@@ -96,11 +100,11 @@ Release management tasks
svn add oak/$version
svn commit -m "Apache Jackrabbit Oak $version release candidate" oak/$version
-9. Find the vote template (`./target/checkout/target/vote.txt`) generated by the Maven build and follow the instructions to verify the build yourself
-10. 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))
-11. Mark the version as released in Jira: [Jackrabbit Jira](https://issues.apache.org/jira/plugins/servlet/project-config/JCR/versions),
+11. Find the vote template (`./target/checkout/target/vote.txt`) generated by the Maven build and follow the instructions to verify the build yourself
+12. 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))
+13. 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.
-12. Wait 72 hours (we usually allow three business days, so be careful when a weekend is ahead)
+14. Wait 72 hours (we usually allow three business days, so be careful when a weekend is ahead)
### Part II: after the release vote