(jackrabbit-site) branch main updated: tune release instructions

[re...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

reschke pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/jackrabbit-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 5ba61883 tune release instructions
5ba61883 is described below

commit 5ba61883948270539b856c1a4e2c10cc19bf83eb
Author: Julian Reschke <ju...@gmx.de>
AuthorDate: Thu Jun 6 06:57:08 2024 +0100

    tune release instructions
---
 src/site/markdown/creating-releases.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/site/markdown/creating-releases.md b/src/site/markdown/creating-releases.md
index f34e170f..3af9461e 100644
--- a/src/site/markdown/creating-releases.md
+++ b/src/site/markdown/creating-releases.md
@@ -157,12 +157,12 @@ Otherwise:
 6. Update the Jackrabbit web site to point to the new release ([GIT](https://github.com/apache/jackrabbit-site)) (the date should be the day when the release was finished).
     * add an entry to `index.md`
     * update `downloads.md` (see [below](#Creating_Markdown_for_Downloads_Page)) - while doing so please a) remove obsoleted entries, and b) move new entries for Jackrabbit and/or Oak to the top)
-    * don't forget to deploy the site (`mvn site-deploy`)
+    * site will be updated by github actions (previously: by deploying the site (`mvn site-deploy`))
 7. If the release was a Jackrabbit release used in Oak, make sure to also update the dependency (and potentially the Javadoc link) in oak-parent/pom.xml (example: [OAK-4743](https://issues.apache.org/jira/browse/OAK-4743) - the current mapping is Jackrabbit 2.20 -> Oak trunk and Oak 1.22, Jackrabbit 2.16 -> Oak 1.8, Jackrabbit 2.14 -> Oak 1.6, Jackrabbit 2.12 -> Oak 1.4)
 8. 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 and 2.20)
-9. Jackrabbit: If the release was a stable release for which we publish API docs, 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).
+9. 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.20), 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)
+11. Oak: 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)
 12. 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` -- note that mirrors may need up to 12 hours!).