jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From resc...@apache.org
Subject svn commit: r1868747 - /jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Date Tue, 22 Oct 2019 11:42:13 GMT
Author: reschke
Date: Tue Oct 22 11:42:13 2019
New Revision: 1868747

URL: http://svn.apache.org/viewvc?rev=1868747&view=rev
Log:
Oak releases may require Jackrabbit changes due to jackrabbit-api

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=1868747&r1=1868746&r2=1868747&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Tue Oct 22 11:42:13 2019
@@ -140,9 +140,10 @@ Otherwise:
     * don't forget to deploy the site (`mvn site-deploy`)
 7. Send a release announcement to the [applicable mailing lists](mailto:announce@apache.org,announce@jackrabbit.apache.org,users@jackrabbit.apache.org,dev@jackrabbit.apache.org,oak-dev@jackrabbit.apache.org?subject=%5BANNOUNCE%5D%20Apache%20Jackrabbit%20...%20released)
once the web site and download mirrors have been synced (template generated in `./target/checkout/target/announcement.txt`).
Please note the announce mails needs to be sent from an @apache.org address.
 8. 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.18 -> Oak trunk and 1.10, Jackrabbit 2.16 -> Oak
1.8, Jackrabbit 2.14 -> Oak 1.6, Jackrabbit 2.12 -> Oak 1.4 and 1.2, Jackrabbit 2.8
-> Oak 1.0)
-9. If the release was a stable release for which we publish API docs (such as Jackrabbit),
consider updating the live site (https://svn.apache.org/repos/asf/jackrabbit/site/live/ -
when producing the API docs, use a checkout of the actual release, specify an English locale
(-Dlocale=en) and try to pick the right JDK version to minimize changes over the previously
checked in docs).
-10. If the release was a stable release that is used for the baseline check in trunk (right
now: Jackrabbit 2.18 and Oak 1.10), update trunk accordingly (example: [JCR-4312](https://issues.apache.org/jira/browse/JCR-4312))
-11. Check that all subprojects now have the correct version; if not, fix them (for instance,
oak-doc and oak-doc-railroad-macro are not in the reactor pom and therefore not updated)
+9. If the release was an Oak release used in Jackrabbit (for jackrabbit-api), make sure to
also update the dependency in jackrabbit-parent/pom.xml (example: [JCR-4492](https://issues.apache.org/jira/browse/JCR-4492)
- the current mapping is Oak latest stable -> Jackrabbit trunk)                  
+10. If the release was a stable release for which we publish API docs (such as Jackrabbit),
consider updating the live site (https://svn.apache.org/repos/asf/jackrabbit/site/live/ -
when producing the API docs, use a checkout of the actual release, specify an English locale
(-Dlocale=en) and try to pick the right JDK version to minimize changes over the previously
checked in docs).
+11. If the release was a stable release that is used for the baseline check in trunk (right
now: Jackrabbit 2.18 and Oak 1.10), update trunk accordingly (example: [JCR-4312](https://issues.apache.org/jira/browse/JCR-4312))
+12. Check that all subprojects now have the correct version; if not, fix them (for instance,
oak-doc and oak-doc-railroad-macro are not in the reactor pom and therefore not updated)
 
 Steps to build the release artifacts
 ------------------------------------



Mime
View raw message