You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@isis.apache.org by da...@apache.org on 2015/08/25 20:35:17 UTC
[1/2] isis-site git commit: ISIS-1052: updates to release docs
Repository: isis-site
Updated Branches:
refs/heads/asf-site bea6c37ae -> 0d1b8b7a0
ISIS-1052: updates to release docs
Project: http://git-wip-us.apache.org/repos/asf/isis-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/isis-site/commit/eb5696cf
Tree: http://git-wip-us.apache.org/repos/asf/isis-site/tree/eb5696cf
Diff: http://git-wip-us.apache.org/repos/asf/isis-site/diff/eb5696cf
Branch: refs/heads/asf-site
Commit: eb5696cff0fa0c9495aea7efa18726955a55af30
Parents: bea6c37
Author: Dan Haywood <da...@haywood-associates.co.uk>
Authored: Tue Aug 25 09:31:51 2015 +0100
Committer: Dan Haywood <da...@haywood-associates.co.uk>
Committed: Tue Aug 25 09:31:51 2015 +0100
----------------------------------------------------------------------
content/documentation.html | 2 +-
content/guides/cg.html | 67 +++++++++++------------------------------
2 files changed, 19 insertions(+), 50 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/isis-site/blob/eb5696cf/content/documentation.html
----------------------------------------------------------------------
diff --git a/content/documentation.html b/content/documentation.html
index 2895790..d4bede8 100644
--- a/content/documentation.html
+++ b/content/documentation.html
@@ -666,7 +666,7 @@ table.CodeRay td.code>pre{padding:0}
<p><a href="./guides/cg.html#_cg_contributing">Contributing patches</a> (pull requests)</p>
</li>
<li>
-<p><a href="./guides/cg.html#_cg_committers_release-process">Cutting a release</a></p>
+<p><a href="./guides/cg.html#_cg_committers_cutting-a-release">Cutting a release</a></p>
</li>
<li>
<p><a href="./guides/cg.html#_cg_committers_verifying-releases">Verifying a release</a></p>
http://git-wip-us.apache.org/repos/asf/isis-site/blob/eb5696cf/content/guides/cg.html
----------------------------------------------------------------------
diff --git a/content/guides/cg.html b/content/guides/cg.html
index 030b50c..17237dd 100644
--- a/content/guides/cg.html
+++ b/content/guides/cg.html
@@ -2822,7 +2822,7 @@ git checkout -b isis-1.9.0</code></pre>
</div>
<div class="listingblock">
<div class="content">
-<pre class="CodeRay highlight"><code data-lang="bash">grep SNAPSHOT `/bin/find . -name pom.xml | grep -v target | sort`</code></pre>
+<pre class="CodeRay highlight"><code data-lang="bash">grep SNAPSHOT `/bin/find . -name pom.xml | grep -v target | grep -v mothball | sort`</code></pre>
</div>
</div>
<div class="paragraph">
@@ -2891,7 +2891,8 @@ env | grep ISIS | sort</code></pre>
<div class="listingblock">
<div class="content">
<pre class="CodeRay highlight"><code data-lang="bash">mvn org.apache.rat:apache-rat-plugin:check -D rat.numUnapprovedLicenses=50 -o && \
-for a in `/bin/find . -name rat.txt -print`; do grep '!???' $a; done</code></pre>
+for a in `/bin/find . -name rat.txt -print`; do grep '!???' $a; done || \
+for a in `/bin/find . -name rat.txt -print`; do grep '!AL' $a; done</code></pre>
</div>
</div>
<div class="paragraph">
@@ -2969,20 +2970,6 @@ licenses to remove from supplemental-models.xml (are spurious):
<div class="paragraph">
<p>If any missing entries are listed or are spurious, then update <code>supplemental-models.xml</code> and try again.</p>
</div>
-<div class="admonitionblock note">
-<table>
-<tr>
-<td class="icon">
-<i class="fa icon-note" title="Note"></i>
-</td>
-<td class="content">
-<div class="paragraph">
-<p>Ignore any missing license warnings for the TCK modules; this is a result of the TCK modules for the viewers (eg <code>isis-viewer-bdd-concordion-tck</code>) depending on the TCK dom, fixtures etc.</p>
-</div>
-</td>
-</tr>
-</table>
-</div>
</div>
<div class="sect4">
<h5 id="_commit_changes">Commit changes</h5>
@@ -3076,7 +3063,7 @@ What is the release version for "Apache Isis Core"? (org.apache.isis.c
</div>
<div class="listingblock">
<div class="content">
-<pre class="CodeRay highlight"><code data-lang="bash">mvn release:prepare -P apache-release -D resume=false -DskipTests=true
+<pre class="CodeRay highlight"><code data-lang="bash">mvn release:prepare -P apache-release -D resume=false -DskipTests=true \
-DreleaseVersion=$ISISREL \
-Dtag=$ISISART-$ISISREL \
-DdevelopmentVersion=$ISISDEV</code></pre>
@@ -3257,8 +3244,9 @@ env | grep ISIS | sort</code></pre>
</div>
<div class="listingblock">
<div class="content">
-<pre class="CodeRay highlight"><code data-lang="bash">mvn org.apache.rat:apache-rat-plugin:check -D rat.numUnapprovedLicenses=50 -o
-for a in `/bin/find . -name rat.txt -print`; do grep '!???' $a; done</code></pre>
+<pre class="CodeRay highlight"><code data-lang="bash">mvn org.apache.rat:apache-rat-plugin:check -D rat.numUnapprovedLicenses=50 -o && \
+for a in `/bin/find . -name rat.txt -print`; do grep '!???' $a; done || \
+for a in `/bin/find . -name rat.txt -print`; do grep '!AL' $a; done</code></pre>
</div>
</div>
<div class="paragraph">
@@ -3270,13 +3258,13 @@ for a in `/bin/find . -name rat.txt -print`; do grep '!???' $a; done</code></pre
<p>first, as self-hosted webconsole (browse to <a href="http://localhost:8080">http://localhost:8080</a>):<br></p>
<div class="listingblock">
<div class="content">
-<pre class="CodeRay highlight"><code data-lang="bash">mvn clean install
+<pre class="CodeRay highlight"><code data-lang="bash">mvn clean install && \
mvn antrun:run -P self-host</code></pre>
</div>
</div>
</li>
<li>
-<p>then using mvn jetty plugin (browse to <a href="http://localhost:8080/simpleapp-webapp/">http://localhost:8080/simpleapp-webapp/</a>):<br></p>
+<p>then using mvn jetty plugin (browse to <a href="http://localhost:8080">http://localhost:8080</a>):<br></p>
<div class="listingblock">
<div class="content">
<pre class="CodeRay highlight"><code data-lang="bash">cd webapp
@@ -3329,33 +3317,17 @@ rm -rf $ISISTMP/checkout
mvn release:prepare -P apache-release \
-DreleaseVersion=$ISISREL \
-DdevelopmentVersion=$ISISDEV \
- -Dtag=$ISISART-$ISISREL
-mvn release:perform -P apache-release \
- -DworkingDirectory=$ISISTMP/checkout</code></pre>
+ -Dtag=$ISISART-$ISISREL</code></pre>
</div>
</div>
</div>
<div class="sect4">
<h5 id="_post_prepare_sanity_check_2">Post-prepare sanity check</h5>
<div class="paragraph">
-<p>This is a good point to test the archetype; nothing has yet been uploaded.
-First, build the archetype:</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="CodeRay highlight"><code data-lang="bash">cd target/generated-sources/archetype
-mvn clean install
-cd ../../..</code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>Then, <em>in a different session</em>, create a new app from the archetype:</p>
-</div>
-<div class="paragraph">
-<p>Set up environment variables:</p>
+<p>This is a good point to test the archetype; nothing has yet been uploaded.</p>
</div>
<div class="paragraph">
-<p>To test the <strong>simpleapp</strong> archetype:</p>
+<p><em>In a different session</em>, create a new app from the archetype. First set up environment variables:</p>
</div>
<div class="listingblock">
<div class="content">
@@ -3365,7 +3337,7 @@ env | grep ISIS | sort</code></pre>
</div>
</div>
<div class="paragraph">
-<p>Then recreate:</p>
+<p>Then generate a new app from the archetype:</p>
</div>
<div class="listingblock">
<div class="content">
@@ -3397,20 +3369,17 @@ mvn jetty:run # runs as mvn jetty plugin</code></pre>
<div class="sect4">
<h5 id="_release_perform_upload_2">Release Perform (upload)</h5>
<div class="paragraph">
-<p>Still in the <strong>archetype</strong> directory and execute the <code>release:perform</code> to upload the artifacts to the ASF Nexus repository:</p>
+<p>Back in the original session (in the <strong>archetype</strong> directory, <code>example/archetype/$ISISCPN</code>), execute <code>release:perform</code>:</p>
</div>
<div class="listingblock">
<div class="content">
-<pre class="CodeRay highlight"><code>cd ../../../example/archetype/$ISISCPN
-rm -rf $ISISTMP/checkout
-mvn release:prepare -P apache-release \
- -DreleaseVersion=$ISISREL \
- -DdevelopmentVersion=$ISISDEV \
- -Dtag=$ISISART-$ISISREL
-mvn release:perform -P apache-release \
+<pre class="CodeRay highlight"><code>mvn release:perform -P apache-release \
-DworkingDirectory=$ISISTMP/checkout</code></pre>
</div>
</div>
+<div class="paragraph">
+<p>This will upload the artifacts to the ASF Nexus repository.</p>
+</div>
</div>
</div>
<div class="sect3">
[2/2] isis-site git commit: ISIS-1052: updates to release docs
Posted by da...@apache.org.
ISIS-1052: updates to release docs
Project: http://git-wip-us.apache.org/repos/asf/isis-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/isis-site/commit/0d1b8b7a
Tree: http://git-wip-us.apache.org/repos/asf/isis-site/tree/0d1b8b7a
Diff: http://git-wip-us.apache.org/repos/asf/isis-site/diff/0d1b8b7a
Branch: refs/heads/asf-site
Commit: 0d1b8b7a05ef840149462b30b5f3064bcaed31db
Parents: eb5696c
Author: Dan Haywood <da...@haywood-associates.co.uk>
Authored: Tue Aug 25 19:33:27 2015 +0100
Committer: Dan Haywood <da...@haywood-associates.co.uk>
Committed: Tue Aug 25 19:33:27 2015 +0100
----------------------------------------------------------------------
content/guides/cg.html | 124 ++++++++++++++++++++++----------------------
1 file changed, 62 insertions(+), 62 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/isis-site/blob/0d1b8b7a/content/guides/cg.html
----------------------------------------------------------------------
diff --git a/content/guides/cg.html b/content/guides/cg.html
index 17237dd..350f04a 100644
--- a/content/guides/cg.html
+++ b/content/guides/cg.html
@@ -2748,10 +2748,10 @@ git checkout master && git merge --no-ff ISIS-1162_pr-31 && git
<p>the release manager cutting the release (documented below)</p>
</li>
<li>
-<p>Members of the Apache Isis PMC voting on the release (documented <a href="#_cg_committers_verifying-releases">here</a>)</p>
+<p>Members of the Apache Isis PMC <a href="#_cg_committers_verifying-releases">verifying</a> and voting on the release</p>
</li>
<li>
-<p>the release manager performing post-release tasks (documented <a href="#_cg_committers_post-release-successful">here if vote was successful</a>, or <a href="#_cg_committers_post-release-unsuccessful">here if unsuccessful</a>).</p>
+<p>the release manager performing post-release tasks, for either a <a href="#_cg_committers_post-release-successful">successful</a> or an <a href="#_cg_committers_post-release-unsuccessful">unsuccessful</a> vote.</p>
</li>
</ul>
</div>
@@ -2778,7 +2778,7 @@ git checkout master && git merge --no-ff ISIS-1162_pr-31 && git
<p>These release notes using bash command line tools. They should work on Linux and MacOS; for Windows, use mSysGit.</p>
</div>
<div class="sect3">
-<h4 id="_obtain_consensus">10.2.1. Obtain Consensus</h4>
+<h4 id="_cg_committers_cutting-a-release_obtain-consensus">10.2.1. Obtain Consensus</h4>
<div class="paragraph">
<p>Before releasing <code>core</code>, ensure there is consensus on the <a href="../support.html">dev mailing list</a> that this is the right time for a release. The discussion should include confirming the version number to be used, and to confirm content.</p>
</div>
@@ -2790,7 +2790,7 @@ git checkout master && git merge --no-ff ISIS-1162_pr-31 && git
</div>
</div>
<div class="sect3">
-<h4 id="_pull_down_code_to_release">10.2.2. Pull down code to release</h4>
+<h4 id="_cg_committers_cutting-a-release_pull-down-code-to-release">10.2.2. Pull down code to release</h4>
<div class="paragraph">
<p>Set the HEAD of your local git repo to the commit to be released. This will usually be the tip of the origin’s <code>master</code> branch. Then, create a release branch for the version number being released; eg:</p>
</div>
@@ -2844,7 +2844,7 @@ git checkout -b isis-1.9.0</code></pre>
</div>
</div>
<div class="sect3">
-<h4 id="_releasing_core">10.2.3. Releasing Core</h4>
+<h4 id="_cg_committers_cutting-a-release_releasing-core">10.2.3. Releasing Core</h4>
<div class="paragraph">
<p>First, we release <code>core</code>. Switch to the appropriate directory:</p>
</div>
@@ -2854,7 +2854,7 @@ git checkout -b isis-1.9.0</code></pre>
</div>
</div>
<div class="sect4">
-<h5 id="_set_environment_variables">Set environment variables</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-core_set-environment-variables">Set environment variables</h5>
<div class="paragraph">
<p>We use environment variables to parameterize as many of the steps as possible.</p>
</div>
@@ -2881,7 +2881,7 @@ env | grep ISIS | sort</code></pre>
</div>
</div>
<div class="sect4">
-<h5 id="_license_headers">License headers</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-core_license-headers">License headers</h5>
<div class="paragraph">
<p>The Apache Release Audit Tool <code>RAT</code> (from the <a href="http://creadur.apache.org">Apache Creadur</a> project) checks for missing license header files. The parent <code>pom.xml</code> of each releasable module specifies the RAT Maven plugin, with a number of custom exclusions.</p>
</div>
@@ -2933,7 +2933,7 @@ for a in `find . -name rat.txt -print`; do grep '!???' $a; done</code></pre>
</div>
</div>
<div class="sect4">
-<h5 id="_missing_license_check">Missing License Check</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-core_missing-license-check">Missing License Check</h5>
<div class="paragraph">
<p>Although Apache Isis has no dependencies on artifacts with incompatible licenses, the POMs for some of these dependencies (in the Maven central repo) do not necessarily contain the required license information. Without appropriate additional configuration, this would result in the generated <code>DEPENDENCIES</code> file and generated Maven site indicating dependencies as having "unknown" licenses.</p>
</div>
@@ -2972,7 +2972,7 @@ licenses to remove from supplemental-models.xml (are spurious):
</div>
</div>
<div class="sect4">
-<h5 id="_commit_changes">Commit changes</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-core_commit-changes">Commit changes</h5>
<div class="paragraph">
<p>Commit any changes from the preceding steps:</p>
</div>
@@ -2983,7 +2983,7 @@ licenses to remove from supplemental-models.xml (are spurious):
</div>
</div>
<div class="sect4">
-<h5 id="_sanity_check">Sanity check</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-core_sanity-check">Sanity check</h5>
<div class="paragraph">
<p>Perform one last sanity check on the codebase. Delete all Isis artifacts from your local Maven repo, then build using the <code>-o</code> offline flag:</p>
</div>
@@ -2995,7 +2995,7 @@ mvn clean install -o</code></pre>
</div>
</div>
<div class="sect4">
-<h5 id="_release_prepare_dry_run">Release prepare "dry run"</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-core_release-prepare-dry-run">Release prepare "dry run"</h5>
<div class="paragraph">
<p>Most of the work is done using the <code>mvn release:prepare</code> goal. Since this makes a lot of changes, we run it first in "dry run" mode; only if that works do we run the goal for real.</p>
</div>
@@ -3057,7 +3057,7 @@ What is the release version for "Apache Isis Core"? (org.apache.isis.c
</div>
</div>
<div class="sect4">
-<h5 id="_release_prepare_proper">Release prepare "proper"</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-core_release-prepare-proper">Release prepare "proper"</h5>
<div class="paragraph">
<p>Assuming this completes successfully, re-run the command, but without the <code>dryRun</code> flag and specifying <code>resume=false</code> (to ignore the generated <code>release.properties</code> file that gets generated as a side-effect of using <code>git</code>). You can also set the <code>skipTests</code> flag since they would have been run during the previous dry run:</p>
</div>
@@ -3085,7 +3085,7 @@ What is the release version for "Apache Isis Core"? (org.apache.isis.c
</div>
</div>
<div class="sect4">
-<h5 id="_post_prepare_sanity_check">Post-prepare sanity check</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-core_post-prepare-sanity-check">Post-prepare sanity check</h5>
<div class="paragraph">
<p>You should end up with artifacts in your local repo with the new version (eg <code>1.9.0</code>). This is a good time to do some quick sanity checks; nothing has yet been uploaded:</p>
</div>
@@ -3128,7 +3128,7 @@ popd</code></pre>
</div>
</div>
<div class="sect4">
-<h5 id="_release_perform_upload">Release perform (Upload)</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-core_release-perform-upload">Release perform (Upload)</h5>
<div class="paragraph">
<p>Once the release has been built locally, it should be uploaded for voting. This is done by deploying the Maven artifacts to a staging directory (this includes the source release ZIP file which will be voted upon).</p>
</div>
@@ -3179,7 +3179,7 @@ re
</div>
</div>
<div class="sect3">
-<h4 id="_releasing_the_archetype">10.2.4. Releasing the Archetype</h4>
+<h4 id="_cg_committers_cutting-a-release_releasing-the-archetype">10.2.4. Releasing the Archetype</h4>
<div class="paragraph">
<p>Apache Isis archetypes are reverse engineered from example applications. Once reverse engineered, the source is checked into git (replacing any earlier version of the archetype) and released.</p>
</div>
@@ -3192,7 +3192,7 @@ re
</div>
</div>
<div class="sect4">
-<h5 id="_setup_environment_variables">Setup environment variables</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-the-archetype_setup-environment-variables">Setup environment variables</h5>
<div class="paragraph">
<p>To recreate the <code>simpleapp</code> archetype:</p>
</div>
@@ -3227,7 +3227,7 @@ env | grep ISIS | sort</code></pre>
</div>
</div>
<div class="sect4">
-<h5 id="_check_the_example_app">Check the example app</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-the-archetype_check-the-example-app">Check the example app</h5>
<div class="paragraph">
<p>Update the parent <code>pom.xml</code> to reference the <em>released</em> version of Apache Isis core, eg:</p>
</div>
@@ -3279,7 +3279,7 @@ mvn jetty:run</code></pre>
</div>
</div>
<div class="sect4">
-<h5 id="_create_the_archetype">Create the archetype</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-the-archetype_create-the-archetype">Create the archetype</h5>
<div class="paragraph">
<p>Make sure you are in the correct directory and environment variables are correct.</p>
</div>
@@ -3306,7 +3306,7 @@ env | grep ISIS | sort</code></pre>
</div>
</div>
<div class="sect4">
-<h5 id="_release_prepare">Release prepare</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-the-archetype_release-prepare">Release prepare</h5>
<div class="paragraph">
<p>Switch to the <strong>archetype</strong> directory and execute the <code>release:prepare</code>:</p>
</div>
@@ -3322,7 +3322,7 @@ mvn release:prepare -P apache-release \
</div>
</div>
<div class="sect4">
-<h5 id="_post_prepare_sanity_check_2">Post-prepare sanity check</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-the-archetype_post-prepare-sanity-check">Post-prepare sanity check</h5>
<div class="paragraph">
<p>This is a good point to test the archetype; nothing has yet been uploaded.</p>
</div>
@@ -3367,7 +3367,7 @@ mvn jetty:run # runs as mvn jetty plugin</code></pre>
</div>
</div>
<div class="sect4">
-<h5 id="_release_perform_upload_2">Release Perform (upload)</h5>
+<h5 id="_cg_committers_cutting-a-release_releasing-the-archetype_release-perform-upload">Release Perform (upload)</h5>
<div class="paragraph">
<p>Back in the original session (in the <strong>archetype</strong> directory, <code>example/archetype/$ISISCPN</code>), execute <code>release:perform</code>:</p>
</div>
@@ -3383,7 +3383,7 @@ mvn jetty:run # runs as mvn jetty plugin</code></pre>
</div>
</div>
<div class="sect3">
-<h4 id="_check_close_staging_repo">10.2.5. Check/Close Staging Repo</h4>
+<h4 id="_cg_committers_cutting-a-release_check-close-staging-repo">10.2.5. Check/Close Staging Repo</h4>
<div class="paragraph">
<p>The <code>mvn release:perform</code> commands will have put release artifacts for both <code>core</code> and the <code>simpleapp</code> archetype into a newly created staging repository on the ASF Nexus repository server.</p>
</div>
@@ -3466,7 +3466,7 @@ mvn jetty:run # runs as mvn jetty plugin</code></pre>
</div>
</div>
<div class="sect3">
-<h4 id="_push_branches">10.2.6. Push branches</h4>
+<h4 id="_cg_committers_cutting-a-release_push-branches">10.2.6. Push branches</h4>
<div class="paragraph">
<p>Push the release branch to origin:</p>
</div>
@@ -3501,7 +3501,7 @@ git fetch</code></pre>
</div>
</div>
<div class="sect3">
-<h4 id="_voting">10.2.7. Voting</h4>
+<h4 id="_cg_committers_cutting-a-release_voting">10.2.7. Voting</h4>
<div class="paragraph">
<p>Once the artifacts have been uploaded, you can call a vote.</p>
</div>
@@ -3509,7 +3509,7 @@ git fetch</code></pre>
<p>In all cases, votes last for 72 hours and require a +3 (binding) vote from members.</p>
</div>
<div class="sect4">
-<h5 id="_start_voting_thread_on_a_href_mailto_e_p_e_g_e_p_e_g_a">Start voting thread on <a href="mailto:dev@isis.apache.org">dev@isis.apache.org</a></h5>
+<h5 id="_cg_committers_cutting-a-release_voting-start-voting-thread">Start voting thread on <a href="mailto:dev@isis.apache.org">dev@isis.apache.org</a></h5>
<div class="paragraph">
<p>The following boilerplate is for a release of the Apache Isis Core. Adapt as required:</p>
</div>
@@ -3578,13 +3578,13 @@ Please verify the release and cast your vote. The vote will be open for a minim
<div class="ulist">
<ul>
<li>
-<p>the release manager cutting the release (documented <a href="#_cg_committers_cutting-a-release">here</a>)</p>
+<p>the release manager <a href="#_cg_committers_cutting-a-release">cutting the release</a></p>
</li>
<li>
-<p>members of the Apache Isis PMC voting on the release (documented below)</p>
+<p>members of the Apache Isis PMC verifying and voting on the release (documented below)</p>
</li>
<li>
-<p>the release manager performing post-release tasks (documented <a href="#_cg_committers_post-release-successful">here if vote was successful</a>, or <a href="#_cg_committers_post-release-unsuccessful">here if unsuccessful</a>).</p>
+<p>the release manager performing post-release tasks, for either a <a href="#_cg_committers_post-release-successful">successful</a> or an <a href="#_cg_committers_post-release-unsuccessful">unsuccessful</a> vote.</p>
</li>
</ul>
</div>
@@ -3935,13 +3935,13 @@ mvn -P self-host antrun:run</code></pre>
<div class="ulist">
<ul>
<li>
-<p>the release manager cutting the release (documented <a href="#_cg_committers_cutting-a-release">here</a>)</p>
+<p>the release manager <a href="#_cg_committers_cutting-a-release">cutting the release</a></p>
</li>
<li>
-<p>members of the Apache Isis PMC voting on the release (documented <a href="#_cg_committers_verifying-releases">here</a>)</p>
+<p>members of the Apache Isis PMC <a href="#_cg_committers_verifying-releases">verifying</a> and voting on the release</p>
</li>
<li>
-<p>the release manager performing post-release tasks (documented below for if vote was successful, else <a href="#_cg_committers_post-release-unsuccessful">here if unsuccessful</a>).</p>
+<p>the release manager performing post-release tasks, for either a successful or an <a href="#_cg_committers_post-release-unsuccessful">unsuccessful</a> vote (former documented below)</p>
</li>
</ul>
</div>
@@ -4311,13 +4311,13 @@ git push</code></pre>
<div class="ulist">
<ul>
<li>
-<p>the release manager cutting the release (documented <a href="#_cg_committers_cutting-a-release">here</a>)</p>
+<p>the release manager <a href="#_cg_committers_cutting-a-release">cutting the release</a></p>
</li>
<li>
-<p>members of the Apache Isis PMC voting on the release (documented <a href="#_cg_committers_verifying-releases">here</a>)</p>
+<p>members of the Apache Isis PMC <a href="#_cg_committers_verifying-releases">verifying</a> and voting on the release</p>
</li>
<li>
-<p>the release manager performing post-release tasks (documented below for if vote was unsuccessful, else <a href="#_cg_committers_post-release-successful">here if successful</a>).</p>
+<p>the release manager performing post-release tasks, for either a <a href="#_cg_committers_post-release-successful">successful</a> or an unsuccessful vote (latter documented below).</p>
</li>
</ul>
</div>
@@ -4325,7 +4325,7 @@ git push</code></pre>
<p>If the vote did not succeed (did not achieve +3 votes after 72 hours and/or is unlikely to do so), then the vote should be closed and the following steps performed.</p>
</div>
<div class="paragraph">
-<p>Note that a release manager may also decide to cancel a vote before 72 hours has elapsed (for example if an error is quicly discovered).</p>
+<p>Note that a release manager may also decide to cancel a vote before 72 hours has elapsed (for example if an error is quickly discovered).</p>
</div>
<div class="sect3">
<h4 id="_inform_dev_ml_2">10.5.1. Inform dev ML</h4>
@@ -4461,7 +4461,7 @@ It is also possible to configure to use <code>.ssh</code> secure keys, and there
</div>
</div>
<div class="sect3">
-<h4 id="_sanity_check_2">10.6.2. Sanity Check</h4>
+<h4 id="_sanity_check">10.6.2. Sanity Check</h4>
<div class="paragraph">
<p>Before deploying the snapshot, perform a quick sanity check.</p>
</div>
@@ -7183,36 +7183,36 @@ xxx<br>
</li>
<li><a href="#_cg_committers_cutting-a-release">10.2. Cutting a Release</a>
<ul class="sectlevel3">
-<li><a href="#_obtain_consensus">10.2.1. Obtain Consensus</a></li>
-<li><a href="#_pull_down_code_to_release">10.2.2. Pull down code to release</a></li>
-<li><a href="#_releasing_core">10.2.3. Releasing Core</a>
+<li><a href="#_cg_committers_cutting-a-release_obtain-consensus">10.2.1. Obtain Consensus</a></li>
+<li><a href="#_cg_committers_cutting-a-release_pull-down-code-to-release">10.2.2. Pull down code to release</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core">10.2.3. Releasing Core</a>
<ul class="sectlevel4">
-<li><a href="#_set_environment_variables">Set environment variables</a></li>
-<li><a href="#_license_headers">License headers</a></li>
-<li><a href="#_missing_license_check">Missing License Check</a></li>
-<li><a href="#_commit_changes">Commit changes</a></li>
-<li><a href="#_sanity_check">Sanity check</a></li>
-<li><a href="#_release_prepare_dry_run">Release prepare "dry run"</a></li>
-<li><a href="#_release_prepare_proper">Release prepare "proper"</a></li>
-<li><a href="#_post_prepare_sanity_check">Post-prepare sanity check</a></li>
-<li><a href="#_release_perform_upload">Release perform (Upload)</a></li>
-</ul>
-</li>
-<li><a href="#_releasing_the_archetype">10.2.4. Releasing the Archetype</a>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core_set-environment-variables">Set environment variables</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core_license-headers">License headers</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core_missing-license-check">Missing License Check</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core_commit-changes">Commit changes</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core_sanity-check">Sanity check</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core_release-prepare-dry-run">Release prepare "dry run"</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core_release-prepare-proper">Release prepare "proper"</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core_post-prepare-sanity-check">Post-prepare sanity check</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-core_release-perform-upload">Release perform (Upload)</a></li>
+</ul>
+</li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-the-archetype">10.2.4. Releasing the Archetype</a>
<ul class="sectlevel4">
-<li><a href="#_setup_environment_variables">Setup environment variables</a></li>
-<li><a href="#_check_the_example_app">Check the example app</a></li>
-<li><a href="#_create_the_archetype">Create the archetype</a></li>
-<li><a href="#_release_prepare">Release prepare</a></li>
-<li><a href="#_post_prepare_sanity_check_2">Post-prepare sanity check</a></li>
-<li><a href="#_release_perform_upload_2">Release Perform (upload)</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-the-archetype_setup-environment-variables">Setup environment variables</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-the-archetype_check-the-example-app">Check the example app</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-the-archetype_create-the-archetype">Create the archetype</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-the-archetype_release-prepare">Release prepare</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-the-archetype_post-prepare-sanity-check">Post-prepare sanity check</a></li>
+<li><a href="#_cg_committers_cutting-a-release_releasing-the-archetype_release-perform-upload">Release Perform (upload)</a></li>
</ul>
</li>
-<li><a href="#_check_close_staging_repo">10.2.5. Check/Close Staging Repo</a></li>
-<li><a href="#_push_branches">10.2.6. Push branches</a></li>
-<li><a href="#_voting">10.2.7. Voting</a>
+<li><a href="#_cg_committers_cutting-a-release_check-close-staging-repo">10.2.5. Check/Close Staging Repo</a></li>
+<li><a href="#_cg_committers_cutting-a-release_push-branches">10.2.6. Push branches</a></li>
+<li><a href="#_cg_committers_cutting-a-release_voting">10.2.7. Voting</a>
<ul class="sectlevel4">
-<li><a href="#_start_voting_thread_on_a_href_mailto_e_p_e_g_e_p_e_g_a">Start voting thread on <a href="mailto:dev@isis.apache.org">dev@isis.apache.org</a></a></li>
+<li><a href="#_cg_committers_cutting-a-release_voting-start-voting-thread">Start voting thread on <a href="mailto:dev@isis.apache.org">dev@isis.apache.org</a></a></li>
</ul>
</li>
</ul>
@@ -7273,7 +7273,7 @@ xxx<br>
<li><a href="#_cg_committers_release-process-for-snapshots">10.6. Snapshot Releases</a>
<ul class="sectlevel3">
<li><a href="#_prerequisites_3">10.6.1. Prerequisites</a></li>
-<li><a href="#_sanity_check_2">10.6.2. Sanity Check</a></li>
+<li><a href="#_sanity_check">10.6.2. Sanity Check</a></li>
<li><a href="#_deploy_all_modules">10.6.3. Deploy All Modules</a></li>
</ul>
</li>