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 fecdc1cc8 Site checkin for project PLC4X: Jenkins Tools
fecdc1cc8 is described below
commit fecdc1cc88743ab19aeb431adf991e7be2b8e304
Author: jenkins <[email protected]>
AuthorDate: Mon Oct 2 11:03:03 2023 +0000
Site checkin for project PLC4X: Jenkins Tools
---
dependency-info.html | 12 +++----
developers/release/release.html | 74 +++++++++++++++++++-------------------
developers/release/validation.html | 6 ++--
summary.html | 2 +-
4 files changed, 47 insertions(+), 47 deletions(-)
diff --git a/dependency-info.html b/dependency-info.html
index fe3367ba8..fa682fb4d 100644
--- a/dependency-info.html
+++ b/dependency-info.html
@@ -128,28 +128,28 @@
<pre><dependency>
<groupId>org.apache.plc4x</groupId>
<artifactId>plc4x-parent</artifactId>
- <version>0.11.0-SNAPSHOT</version>
+ <version>0.12.0-SNAPSHOT</version>
<type>pom</type>
</dependency></pre></div></section><section>
<h3><a name="Apache_Ivy"></a>Apache Ivy</h3><a name="Apache_Ivy"></a>
<div>
-<pre><dependency org="org.apache.plc4x"
name="plc4x-parent" rev="0.11.0-SNAPSHOT">
+<pre><dependency org="org.apache.plc4x"
name="plc4x-parent" rev="0.12.0-SNAPSHOT">
<artifact name="plc4x-parent" type="pom" />
</dependency></pre></div></section><section>
<h3><a name="Groovy_Grape"></a>Groovy Grape</h3><a name="Groovy_Grape"></a>
<div>
<pre>@Grapes(
-@Grab(group='org.apache.plc4x', module='plc4x-parent',
version='0.11.0-SNAPSHOT')
+@Grab(group='org.apache.plc4x', module='plc4x-parent',
version='0.12.0-SNAPSHOT')
)</pre></div></section><section>
<h3><a name="Gradle.2FGrails"></a>Gradle/Grails</h3><a
name="Gradle.2FGrails"></a>
<div>
-<pre>implementation
'org.apache.plc4x:plc4x-parent:0.11.0-SNAPSHOT'</pre></div></section><section>
+<pre>implementation
'org.apache.plc4x:plc4x-parent:0.12.0-SNAPSHOT'</pre></div></section><section>
<h3><a name="Scala_SBT"></a>Scala SBT</h3><a name="Scala_SBT"></a>
<div>
-<pre>libraryDependencies += "org.apache.plc4x" %
"plc4x-parent" %
"0.11.0-SNAPSHOT"</pre></div></section><section>
+<pre>libraryDependencies += "org.apache.plc4x" %
"plc4x-parent" %
"0.12.0-SNAPSHOT"</pre></div></section><section>
<h3><a name="Leiningen"></a>Leiningen</h3><a name="Leiningen"></a>
<div>
-<pre>[org.apache.plc4x/plc4x-parent
"0.11.0-SNAPSHOT"]</pre></div></section></section>
+<pre>[org.apache.plc4x/plc4x-parent
"0.12.0-SNAPSHOT"]</pre></div></section></section>
</main>
<footer class="pt-4 my-md-5 pt-md-5 w-100 border-top">
<div class="row justify-content-md-center" style="font-size: 13px">
diff --git a/developers/release/release.html b/developers/release/release.html
index dbe84684f..0adbedae0 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -270,7 +270,7 @@ Please be sure to execute the release with a Java version
11 or the Karaf featur
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P
with-c,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,enable-all-checks
-DbranchName=rel/{current-short-version}</pre>
</div>
</div>
<div class="ulist checklist">
@@ -285,7 +285,7 @@ Please be sure to execute the release with a Java version
11 or the Karaf featur
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:prepare -P
with-c,with-dotnet,with-go,with-python,with-sandbox</pre>
+<pre> mvn release:prepare -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks</pre>
</div>
</div>
<div class="ulist checklist">
@@ -483,7 +483,7 @@ Usually the <code>NOTICE</code> file has to be adjusted.</p>
<p>For each new Major and Minor release we create a new branch at the
beginning of a code-freeze phase.</p>
</div>
<div class="paragraph">
-<p>So if currently the project version in develop is
<code>0.11.0-SNAPSHOT</code>, we create a branch <code>rel/0.11</code>.</p>
+<p>So if currently the project version in develop is
<code>0.12.0-SNAPSHOT</code>, we create a branch <code>rel/0.12</code>.</p>
</div>
<div class="paragraph">
<p>When creating the branch is exactly the moment in which the version in
<code>develop</code> is incremented to the next minor version.</p>
@@ -501,16 +501,16 @@ 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-c,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,enable-all-checks
-DbranchName=rel/{minor-version}</pre>
</div>
</div>
<div class="paragraph">
<p>Per default the plugin suggests the next bugfix version as working version,
however we want it to use the next minor version.
-So in case of preparing the release branch for <code>0.11.0-SNAPSHOT</code>
the command would be the following:</p>
+So in case of preparing the release branch for <code>0.12.0-SNAPSHOT</code>
the command would be the following:</p>
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P
with-c,with-dotnet,with-go,with-python,with-sandbox -DbranchName=rel/0.11</pre>
+<pre> mvn release:branch -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks
-DbranchName=rel/0.12</pre>
</div>
</div>
<div class="paragraph">
@@ -518,7 +518,7 @@ So in case of preparing the release branch for
<code>0.11.0-SNAPSHOT</code> the
</div>
<div class="listingblock">
<div class="content">
-<pre> What is the new working copy version for "PLC4X"?
(org.apache.plc4x:plc4x-parent) 0.11.1-SNAPSHOT: : 0.12.0-SNAPSHOT</pre>
+<pre> What is the new working copy version for "PLC4X"?
(org.apache.plc4x:plc4x-parent) 0.12.1-SNAPSHOT: : 0.13.0-SNAPSHOT</pre>
</div>
</div>
<div class="paragraph">
@@ -528,7 +528,7 @@ So in case of preparing the release branch for
<code>0.11.0-SNAPSHOT</code> the
<p>This step now should perform quite quickly as no build and no tests are
involved.</p>
</div>
<div class="paragraph">
-<p>However, in the end the versions of the <code>develop</code> branch are
updated and a new <code>rel/0.11</code> branch is created.</p>
+<p>However, in the end the versions of the <code>develop</code> branch are
updated and a new <code>rel/0.12</code> branch is created.</p>
</div>
</div>
<div class="sect2">
@@ -542,7 +542,7 @@ So in case of preparing the release branch for
<code>0.11.0-SNAPSHOT</code> the
<div class="listingblock">
<div class="content">
<pre>==============================================================
-(Unreleased) Apache PLC4X 0.12.0-SNAPSHOT
+(Unreleased) Apache PLC4X 0.13.0-SNAPSHOT
==============================================================
New Features
@@ -602,11 +602,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-c,with-dotnet,with-go,with-python,with-sandbox</pre>
+<pre>mvn release:prepare -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks</pre>
</div>
</div>
<div class="paragraph">
-<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)
+<p>(The <code>-P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks</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">
@@ -615,7 +615,7 @@ In general the plugin will now ask you 3 questions:</p>
<p>The version we want to release as (It will suggest the version you get by
omitting the <code>-SNAPSHOT</code> suffix)</p>
</li>
<li>
-<p>The name of the tag the release commit will be tagged with in the SCM (Name
it <code>v{release-version}</code> (<code>v0.11.0</code> in our case)</p>
+<p>The name of the tag the release commit will be tagged with in the SCM (Name
it <code>v{release-version}</code> (<code>v0.12.0</code> in our case)</p>
</li>
<li>
<p>The next development version (The version present in the pom after the
release) (<code>{current-next-bugfix-version}</code> in our case)</p>
@@ -640,7 +640,7 @@ In general the plugin will now ask you 3 questions:</p>
<p>Run a build with all tests</p>
</li>
<li>
-<p>Commit the changes (commit message: <code>[maven-release-plugin] prepare
release v0.11.0</code>)</p>
+<p>Commit the changes (commit message: <code>[maven-release-plugin] prepare
release v0.12.0</code>)</p>
</li>
<li>
<p>Push the commit</p>
@@ -672,7 +672,7 @@ is in the correct state. Please select the release branch
and verify the commit
</div>
</div>
<div class="paragraph">
-<p>It is important that the commit with the message "[maven-release-plugin]
prepare release v{release-version}" is tagged with the release tag (in this
case v0.11.0)</p>
+<p>It is important that the commit with the message "[maven-release-plugin]
prepare release v{release-version}" is tagged with the release tag (in this
case v0.12.0)</p>
</div>
<div class="paragraph">
<p>If you check the commit itself, it should mainly consist of version updates
like this:</p>
@@ -719,7 +719,7 @@ If the commit history doesn’t look like this,
something went wrong.
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:rollback -P
with-c,with-dotnet,with-go,with-python,with-sandbox</pre>
+<pre>mvn release:rollback -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks</pre>
</div>
</div>
<div class="paragraph">
@@ -819,13 +819,13 @@ Here it automatically executes a maven build (You
don’t have to do this, i
<div class="listingblock">
<div class="content">
<pre> ./KEYS
- ./0.11.0/
- ./0.11.0/rc1
- ./0.11.0/rc1/README
- ./0.11.0/rc1/RELEASE_NOTES
- ./0.11.0/rc1/apache-plc4x-0.11.0-source-release.zip
- ./0.11.0/rc1/apache-plc4x-0.11.0-source-release.zip.asc
- ./0.11.0/rc1/apache-plc4x-0.11.0-source-release.zip.sha512</pre>
+ ./0.12.0/
+ ./0.12.0/rc1
+ ./0.12.0/rc1/README
+ ./0.12.0/rc1/RELEASE_NOTES
+ ./0.12.0/rc1/apache-plc4x-0.12.0-source-release.zip
+ ./0.12.0/rc1/apache-plc4x-0.12.0-source-release.zip.asc
+ ./0.12.0/rc1/apache-plc4x-0.12.0-source-release.zip.sha512</pre>
</div>
</div>
<div class="paragraph">
@@ -868,17 +868,17 @@ The following would be the one used to do our first TLP
release:</p>
<div class="listingblock">
<div class="content">
<pre>E-Mail Topic:
-[VOTE] Apache PLC4X 0.11.0 RC1
+[VOTE] Apache PLC4X 0.12.0 RC1
Message:
-Apache PLC4X 0.11.0 has been staged under [2] and it’s time to vote
+Apache PLC4X 0.12.0 has been staged under [2] and it’s time to vote
on accepting it for release. All Maven artifacts are available under [1].
Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.
-Release tag: v0.11.0
+Release tag: v0.12.0
Hash for the release tag: {replacethiswiththerealgitcommittag}
Per [3] "Before voting +1 PMC members are required to download
@@ -894,7 +894,7 @@ You can achieve the above by following [4].
[1]
https://repository.apache.org/content/repositories/orgapacheplc4x-{somefourdigitnumber}
-[2] https://dist.apache.org/repos/dist/dev/plc4x/0.11.0/rc1
+[2] https://dist.apache.org/repos/dist/dev/plc4x/0.12.0/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4]
https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release</pre>
</div>
@@ -905,7 +905,7 @@ You can achieve the above by following [4].
<div class="listingblock">
<div class="content">
<pre>E-Mail Topic:
-[DISCUSS] Apache PLC4X 0.11.0 RC1
+[DISCUSS] Apache PLC4X 0.12.0 RC1
Message:
This is the discussion thread for the corresponding VOTE thread.
@@ -930,7 +930,7 @@ If you have to vote -1 please mention a brief description
on why and then take t
<div class="listingblock">
<div class="content">
<pre>E-Mail Topic:
-[RESULT] [VOTE] Apache PLC4X 0.11.0 RC1
+[RESULT] [VOTE] Apache PLC4X 0.12.0 RC1
Message:
So, the vote passes with {number of +1 votes} +1 votes by PMC members {number
of +1 votes from non-pmc members} +1 vote by a non PMC member.</pre>
@@ -945,9 +945,9 @@ This is done by moving them inside the Apache SVN.</p>
</div>
<div class="listingblock">
<div class="content">
-<pre> svn move -m "Release Apache PLC4X 0.11.0" \
- https://dist.apache.org/repos/dist/dev/plc4x/0.11.0/rc1 \
- https://dist.apache.org/repos/dist/release/plc4x/0.11.0</pre>
+<pre> svn move -m "Release Apache PLC4X 0.12.0" \
+ https://dist.apache.org/repos/dist/dev/plc4x/0.12.0/rc1 \
+ https://dist.apache.org/repos/dist/release/plc4x/0.12.0</pre>
</div>
</div>
<div class="paragraph">
@@ -968,7 +968,7 @@ This is done by moving them inside the Apache SVN.</p>
<p>Set the versions of the release branch to the previous version by using the
<code>versions:set</code> plugin:</p>
<div class="literalblock">
<div class="content">
-<pre>mvn versions:set -DprocessAllModules=true -P
with-c,with-dotnet,with-go,with-python,with-sandbox</pre>
+<pre>mvn versions:set -DprocessAllModules=true -P
with-c,with-dotnet,with-go,with-python,with-sandbox,enable-all-checks</pre>
</div>
</div>
</li>
@@ -1072,7 +1072,7 @@ This has to be done with git</p>
<div class="listingblock">
<div class="content">
<pre>git checkout release
-git merge v0.11.0</pre>
+git merge v0.12.0</pre>
</div>
</div>
<div class="paragraph">
@@ -1080,7 +1080,7 @@ git merge v0.11.0</pre>
</div>
<div class="listingblock">
<div class="content">
-<pre>git merge -X theirs v0.11.0</pre>
+<pre>git merge -X theirs v0.12.0</pre>
</div>
</div>
<div class="paragraph">
@@ -1113,7 +1113,7 @@ This is done by changing the <code>download.adoc</code>
under <code>src/site/use
<p>Copy the last release down to <em>Previous Releases</em></p>
</li>
<li>
-<p>Point the download links of the last release to archive, e.g. <code><a
href="http://archive.apache.org/dist/plc4x/0.11.0/apache-plc4x-0.11.0-source-release.zip";
class="bare">http://archive.apache.org/dist/plc4x/0.11.0/apache-plc4x-0.11.0-source-release.zip</a></code></p>
+<p>Point the download links of the last release to archive, e.g. <code><a
href="http://archive.apache.org/dist/plc4x/0.12.0/apache-plc4x-0.12.0-source-release.zip";
class="bare">http://archive.apache.org/dist/plc4x/0.12.0/apache-plc4x-0.12.0-source-release.zip</a></code></p>
</li>
<li>
<p>Add the new Release under <em>Current Releases</em> and change all links.
@@ -1146,10 +1146,10 @@ CC:
[email protected]
E-Mail Topic:
-[ANNOUNCE] Apache PLC4X 0.11.0 released
+[ANNOUNCE] Apache PLC4X 0.12.0 released
Message:
-The Apache PLC4X team is pleased to announce the release of Apache PLC4X 0.11.0
+The Apache PLC4X team is pleased to announce the release of Apache PLC4X 0.12.0
PLC4X is a set of libraries for communicating with industrial programmable
logic controllers (PLCs) using a variety of protocols but with a shared API.
diff --git a/developers/release/validation.html
b/developers/release/validation.html
index 4e8de3c12..71e1e9f90 100644
--- a/developers/release/validation.html
+++ b/developers/release/validation.html
@@ -391,7 +391,7 @@ Especially in the <code>sandbox</code> there may be parts
that are not formally
</div>
<div class="listingblock">
<div class="content">
-<pre>java -jar apache-rat-0.13.jar apache-plc4x-0.11.0-source-release.zip >
rat.log</pre>
+<pre>java -jar apache-rat-0.13.jar apache-plc4x-0.12.0-source-release.zip >
rat.log</pre>
</div>
</div>
<div class="paragraph">
@@ -408,11 +408,11 @@ Especially in the <code>sandbox</code> there may be parts
that are not formally
</div>
<div class="listingblock">
<div class="content">
-<pre>tools/download_staged_release.sh 0.11.0 1</pre>
+<pre>tools/download_staged_release.sh 0.12.0 1</pre>
</div>
</div>
<div class="paragraph">
-<p>This will download all the files into a directory:
<code>downloaded-plc4x-0.11.01</code>.</p>
+<p>This will download all the files into a directory:
<code>downloaded-plc4x-0.12.01</code>.</p>
</div>
<div class="paragraph">
<p>After that it will calculate the SHA512 hash and compare it with the staged
hash.</p>
diff --git a/summary.html b/summary.html
index 9213dc028..677b1a7a7 100644
--- a/summary.html
+++ b/summary.html
@@ -162,7 +162,7 @@
<td>plc4x-parent</td></tr>
<tr class="b">
<td align="left">Version</td>
-<td>0.11.0-SNAPSHOT</td></tr>
+<td>0.12.0-SNAPSHOT</td></tr>
<tr class="a">
<td align="left">Type</td>
<td>pom</td></tr></table></section></section>
