This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/plc4x-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 8d57249 Site checkin for project PLC4X: Jenkins Tools
8d57249 is described below
commit 8d57249e243d7b133d390e48b68aa64aa8d85500
Author: jenkins <[email protected]>
AuthorDate: Fri Sep 10 11:32:29 2021 +0000
Site checkin for project PLC4X: Jenkins Tools
---
developers/release/release.html | 14 +++++++-------
developers/release/validation.html | 33 +++++++++++++++++++++++++++++++--
2 files changed, 38 insertions(+), 9 deletions(-)
diff --git a/developers/release/release.html b/developers/release/release.html
index 4dae04e..1906f7c 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -255,7 +255,7 @@ Please be sure to execute the release with a Java version
between 1.8 and 11 or
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P
with-boost,with-c,with-docker,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/{current-short-version}</pre>
+<pre> mvn release:branch -P
with-c,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/{current-short-version}</pre>
</div>
</div>
<div class="ulist checklist">
@@ -270,7 +270,7 @@ Please be sure to execute the release with a Java version
between 1.8 and 11 or
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:prepare -P
with-boost,with-c,with-docker,with-dotnet,with-go,with-python,with-sandbox</pre>
+<pre> mvn release:prepare -P
with-c,with-dotnet,with-go,with-python,with-sandbox</pre>
</div>
</div>
<div class="ulist checklist">
@@ -471,7 +471,7 @@ Otherwise, the non-default modules on develop will
reference the old version whi
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:branch -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/{minor-version}</pre>
+<pre>mvn release:branch -P with-c,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/{minor-version}</pre>
</div>
</div>
<div class="paragraph">
@@ -480,7 +480,7 @@ So in case of preparing the release branch for
<code>0.9.0-SNAPSHOT</code> the c
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-go,with-python,with-sandbox
-DbranchName=rel/0.9</pre>
+<pre> mvn release:branch -P
with-c,with-dotnet,with-go,with-python,with-sandbox -DbranchName=rel/0.9</pre>
</div>
</div>
<div class="paragraph">
@@ -572,11 +572,11 @@ In order to prepare a release-candidate, the first step
is switching to the corr
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:prepare -P
with-boost,with-c,with-docker,with-dotnet,with-go,with-python,with-sandbox</pre>
+<pre>mvn release:prepare -P
with-c,with-dotnet,with-go,with-python,with-sandbox</pre>
</div>
</div>
<div class="paragraph">
-<p>(The <code>-P
with-boost,with-c,with-docker,with-dotnet,with-go,with-python,with-sandbox</code>
tells maven to activate the all profiles that partition the build and makes
sure the versions of all modules are updated as part of the release)
+<p>(The <code>-P with-c,with-dotnet,with-go,with-python,with-sandbox</code>
tells maven to activate the all profiles that partition the build and makes
sure the versions of all modules are updated as part of the release)
In general the plugin will now ask you 3 questions:</p>
</div>
<div class="olist arabic">
@@ -705,7 +705,7 @@ If the commit history doesn’t look like this,
something went wrong.
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:perform -DreleaseProfiles=apache-release</pre>
+<pre>mvn release:perform</pre>
</div>
</div>
<div class="paragraph">
diff --git a/developers/release/validation.html
b/developers/release/validation.html
index 039bcef..f2fb260 100644
--- a/developers/release/validation.html
+++ b/developers/release/validation.html
@@ -356,7 +356,7 @@ Especially in the <code>sandbox</code> there may be parts
that are not formally
<p><input type="checkbox" data-item-complete="0"/> Build the project according
to the information in the README.md file.</p>
</li>
<li>
-<p><input type="checkbox" data-item-complete="0"/> [RM] Build the project with
all <code>with-xyz</code> profiles and tests enabled and an empty maven local
repo: by appendng <code>-Dmaven.repo.local=../.m2</code>.</p>
+<p><input type="checkbox" data-item-complete="0"/> [RM] Build the project with
all <code>with-xyz</code> profiles and tests enabled and an empty maven local
repo: by appending <code>-Dmaven.repo.local=../.m2</code> (On windows use
<code>-D"maven.repo.local"="../.m2"</code>).</p>
</li>
</ul>
</div>
@@ -386,7 +386,7 @@ Especially in the <code>sandbox</code> there may be parts
that are not formally
<div class="sect2">
<h3 id="release_tooling">Release Tooling</h3>
<div class="paragraph">
-<p>In the <code>tools</code> directory we have a little script that can help
downloading and checking the hashes and signatures automatically.</p>
+<p>In the <code>tools</code> directory we have a little script that can help
with downloading and checking the hashes and signatures automatically.</p>
</div>
<div class="paragraph">
<p>In order to execute this, please change directories into the projects base
directory and execute the following command:</p>
@@ -406,6 +406,35 @@ Especially in the <code>sandbox</code> there may be parts
that are not formally
<p>Last not least it will validate the PGP key and print out some information
on it.</p>
</div>
</div>
+<div class="sect2">
+<h3 id="template_for_the_email_for_voting">Template for the email for
voting</h3>
+<div class="listingblock">
+<div class="content">
+<pre>+1/-1 (binding)
+
+Name
+
+[] Download all staged artifacts under the url specified in the release vote
email.
+[] Verify the signature is correct.
+[] Check if the signature references an Apache email address.
+[] Verify the SHA512 hashes.
+[] Unzip the archive.
+[] Verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the
extracted source bundle.
+[] Verify the content of LICENSE, NOTICE, README, RELEASE_NOTES files in the
extracted source bundle.
+[] [RM] Verify the staged source README, RELEASE_NOTE files correspond to
those in the extracted source bundle.
+[] [RM] Run RAT externally to ensure there are no surprises.
+[] Search for SNAPSHOT references: Only found some in the dummy website copy
in the integration-tests
+[] Search for Copyright references, and if they are in headers, make sure
these files containing them are mentioned in the LICENSE file.
+[] Build the project according to the information in the README.md file.
+[] [RM] Build the project with all with-xyz profiles and tests enabled and an
empty maven local repo.</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>If everything is ok, I put "OK" int the square brackets.
+If there are minor issues, I put "MINOR" in there and, if it’s a short
reason, I put an explanation at the end of the line. If it’s longer I put
a longer section after the checklist.
+If there are major issues, I put "FAIL" in there and comment the same way as
with minor issues.</p>
+</div>
+</div>
</div>
</div>
</main>
