You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by sv...@apache.org on 2026/10/13 16:29:48 UTC
svn commit: r1939092 - jackrabbit/site/live/jcr
Author: svn-site-role
Date: Tue Oct 13 16:29:48 2026
New Revision: 1939092
Log:
@trivial: Site checkin for project Apache Jackrabbit Site-1.0-SNAPSHOT
Modified:
jackrabbit/site/live/jcr/creating-releases.html
Modified: jackrabbit/site/live/jcr/creating-releases.html
==============================================================================
--- jackrabbit/site/live/jcr/creating-releases.html Tue Oct 13 15:29:29 2026 (r1939091)
+++ jackrabbit/site/live/jcr/creating-releases.html Tue Oct 13 16:29:48 2026 (r1939092)
@@ -684,7 +684,7 @@ update the fixVersion information). An e
<p>Also, every ticket resolved in a beta release also should have the next stable branch as “fixVersion” (such as
2.23.n and 2.24). This ensures that 2.24.0, once it is released, will have complete release notes.</p></section><section>
<h2><a name="Appendix_H:_checking_for_dubious_commits"></a>Appendix H: checking for dubious commits</h2>
-<p>There's a (AI generated) <a class="externalLink" href="https://https://dist.apache.org/repos/dist/dev/jackrabbit/check-commits.sh">shell script</a>!</p>
+<p>There's a (AI generated) <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/jackrabbit/check-commits.sh">shell script</a>!</p>
<p>It will check commits since a given tag, and will check for properly set <code>fixVersion</code> fields. Take the output
with a grain of salt. Run it in a local checkout (non-destructive):</p>