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 2022/01/07 17:00:06 UTC

svn commit: r1896815 - /jackrabbit/site/live/jcr/creating-releases.html

Author: reschke
Date: Fri Jan  7 17:00:06 2022
New Revision: 1896815

URL: http://svn.apache.org/viewvc?rev=1896815&view=rev
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
URL: http://svn.apache.org/viewvc/jackrabbit/site/live/jcr/creating-releases.html?rev=1896815&r1=1896814&r2=1896815&view=diff
==============================================================================
--- jackrabbit/site/live/jcr/creating-releases.html (original)
+++ jackrabbit/site/live/jcr/creating-releases.html Fri Jan  7 17:00:06 2022
@@ -1,6 +1,6 @@
 <!DOCTYPE html>
 <!--
- | Generated by Apache Maven Doxia Site Renderer 1.9.2 from src\site\markdown/creating-releases.md at 2021-11-18
+ | Generated by Apache Maven Doxia Site Renderer 1.9.2 from src\site\markdown/creating-releases.md at 2022-01-07
  | Rendered using Apache Maven Fluido Skin 1.9
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en">
@@ -97,7 +97,7 @@
 
         <div id="breadcrumbs">
           <ul class="breadcrumb">
-        <li id="publishDate">Last Published: 2021-11-18</li>
+        <li id="publishDate">Last Published: 2022-01-07</li>
           </ul>
         </div>
       </header>
@@ -210,6 +210,7 @@ git diff jackrabbit-oak-1.8.0 | grep -i
 <li>If this is a release with Java 7 or older, make sure that your <code>MAVEN_OPTS</code> contain <code>-Dhttps.protocols=TLSv1.2</code>.</li>
 <li>When doing &#x201c;stable&#x201d; 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).</li>
 <li>Build and deploy the release artifacts with Maven. See <a href="#Steps_to_build_the_release_artifacts">below</a> for the exact steps.</li>
+<li>Mark the version as released in Jira: <a class="externalLink" href="https://issues.apache.org/jira/plugins/servlet/project-config/JCR/versions">Jackrabbit Jira</a>, <a class="externalLink" href="https://issues.apache.org/jira/plugins/servlet/project-config/OAK/versions">Oak Jira</a>. You&#x2019;ll see all the defined project versions. From the settings menu, choose &#x2018;Release&#x2019; on the version.</li>
 <li>Do a sanity check that the <a class="externalLink" href="https://repository.apache.org/index.html#stagingRepositories">staged repository</a> on repository.apache.org contains all artifacts (~19 projects for Jackrabbit).</li>
 <li>Close the staged repository, giving it a meaningful name, such as &#x201c;Apache Jackrabbit 2.x.y RC&#x201d;</li>
 <li>Upload the artifacts to <a class="externalLink" href="https://dist.apache.org/repos/dist/dev/jackrabbit/">https://dist.apache.org/repos/dist/dev/jackrabbit/</a> as follows:
@@ -242,11 +243,10 @@ svn commit -m &quot;Apache Jackrabbit Oa
 <p>Find the vote template (<code>./target/checkout/target/vote.txt</code>) generated by the Maven build and follow the instructions to verify the build yourself</p>
 </li>
 <li>Start the vote thread by emailing the applicable mailing list (<a class="externalLink" href="mailto:dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20x.y.z">Jackrabbit</a>, <a class="externalLink" href="mailto:oak-dev@jackrabbit.apache.org?subject=%5BVOTE%5D%20Release%20Apache%20Jackrabbit%20Oak%20x.y.z">Oak</a>)</li>
-<li>Mark the version as released in Jira: <a class="externalLink" href="https://issues.apache.org/jira/plugins/servlet/project-config/JCR/versions">Jackrabbit Jira</a>, <a class="externalLink" href="https://issues.apache.org/jira/plugins/servlet/project-config/OAK/versions">Oak Jira</a>. You&#x2019;ll see all the defined project versions. From the settings menu, choose &#x2018;Release&#x2019; on the version.</li>
 <li>Wait 72 hours (we usually allow three business days, so be careful when a weekend is ahead)</li>
 </ol></section><section>
 <h3><a name="Part_II:_after_the_release_vote"></a>Part II: after the release vote</h3>
-<p>If the vote fails (easy case first) remove the tag from svn, drop the staged repository, revert the version release in Jira, and announce that the vote has failed by replying to the vote email.</p>
+<p>If the vote fails (easy case first) remove the tag from source control, drop the staged repository, revert the version release in Jira, and announce that the vote has failed by replying to the vote email.</p>
 <p>Otherwise:</p>
 <ol style="list-style-type: decimal">
 
@@ -278,12 +278,12 @@ https://dist.apache.org/repos/dist/relea
 <li>don&#x2019;t forget to deploy the site (<code>mvn site-deploy</code>)</li>
 </ul>
 </li>
-<li>Send a release announcement to the <a class="externalLink" href="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">applicable mailing lists</a> once the web site and download mirrors have been synced (template generated in <code>./target/checkout/target/announcement.txt</code>). Please note the announce mails needs to be sent from an @apache.org address. In case you are using a mailbox other than apache mailbox (such as gmail) to send mails for your apache address, make sure to send them in plain text format.</li>
-<li>If the release was a Jackrabbit release used in Oak, make sure to also update the dependency (and potentiall the Javadoc link) in oak-parent/pom.xml (example: <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK-4743">OAK-4743</a> - the current mapping is Jackrabbit 2.20 -&gt; Oak trunk and Oak 1.22, Jackrabbit 2.16 -&gt; Oak 1.8, Jackrabbit 2.14 -&gt; Oak 1.6, Jackrabbit 2.12 -&gt; Oak 1.4)</li>
+<li>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: <a class="externalLink" href="https://issues.apache.org/jira/browse/OAK-4743">OAK-4743</a> - the current mapping is Jackrabbit 2.20 -&gt; Oak trunk and Oak 1.22, Jackrabbit 2.16 -&gt; Oak 1.8, Jackrabbit 2.14 -&gt; Oak 1.6, Jackrabbit 2.12 -&gt; Oak 1.4)</li>
 <li>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: <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-4492">JCR-4492</a> - the current mapping is Oak latest stable -&gt; Jackrabbit trunk and 2.20)</li>
 <li>If the release was a stable release for which we publish API docs (such as Jackrabbit), consider updating the live site (<a class="externalLink" href="https://svn.apache.org/repos/asf/jackrabbit/site/live/">https://svn.apache.org/repos/asf/jackrabbit/site/live/</a> - 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).</li>
 <li>If the release was a stable release that is used for the baseline check in trunk (right now: Jackrabbit 2.20 and Oak 1.22), update trunk accordingly (example: <a class="externalLink" href="https://issues.apache.org/jira/browse/JCR-4312">JCR-4312</a>)</li>
 <li>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)</li>
+<li>Send a release announcement to the <a class="externalLink" href="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">applicable mailing lists</a> once the web site and download mirrors have been synced (template generated in <code>./target/checkout/target/announcement.txt</code> &#x2013; note that mirrors may need up to 12 hours!). Please note the announce mails needs to be sent from an @apache.org address. In case you are using a mailbox other than apache mailbox (such as gmail) to send mails for your apache address, make sure to send them in plain text format. (Warning: sending the announcement too early may cause it to be rejected for <a class="externalLink" href="mailto:announce@apache.org">announce@apache.org</a>)</li>
 </ol></section></section><section>
 <h2><a name="Steps_to_build_the_release_artifacts"></a>Steps to build the release artifacts</h2>
 <p>The release is built using the Maven release plugin (if your platform is Windows with Cygwin, see <a href="#Appendix_C:_Cygwin">Appendix C</a>). See the <a class="externalLink" href="https://maven.apache.org/developers/release/maven-project-release-procedure.html">Performing a Maven Project Release</a> guide for more details. Make sure you have added the pgp key information in you maven settings file, especially if you have more than one key installed locally. See <a href="#b">Appendix B</a> for the details.</p>
@@ -455,7 +455,7 @@ mvn release:update-versions -DautoVersio
     <footer>
       <div class="container-fluid">
         <div class="row-fluid">
-            <p>&#169;      2021
+            <p>&#169;      2022
 <a href="https://www.apache.org/">The Apache Software Foundation</a>
 </p>
         </div>