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 b299f9a27 Site checkin for project PLC4X: Jenkins Tools
b299f9a27 is described below
commit b299f9a2770381c35bba43f95e82d99e2ac35b8e
Author: jenkins <bui...@apache.org>
AuthorDate: Tue Sep 26 07:02:38 2023 +0000
Site checkin for project PLC4X: Jenkins Tools
---
dependency-management.html | 8 ++---
developers/release/build-tools.html | 60 ++++++++++++++++++-------------------
plugin-management.html | 2 +-
3 files changed, 35 insertions(+), 35 deletions(-)
diff --git a/dependency-management.html b/dependency-management.html
index 5246d7a81..00d41f3f7 100644
--- a/dependency-management.html
+++ b/dependency-management.html
@@ -689,7 +689,7 @@
<tr class="a">
<td align="left">nl.jqno.equalsverifier</td>
<td><a class="externalLink"
href="https://www.jqno.nl/equalsverifier";>equalsverifier</a></td>
-<td>3.15.1</td>
+<td>3.15.2</td>
<td>-</td>
<td>jar</td>
<td><a class="externalLink"
href="https://www.apache.org/licenses/LICENSE-2.0.txt";>Apache License, Version
2.0</a></td></tr>
@@ -787,21 +787,21 @@
<tr class="a">
<td align="left">org.apache.plc4x.plugins</td>
<td><a class="externalLink"
href="https://www.apache.org/plc4x-code-generation/plc4x-code-generation-language-base/";>plc4x-code-generation-language-base</a></td>
-<td>1.7.0-SNAPSHOT</td>
+<td>1.7.0</td>
<td>-</td>
<td>jar</td>
<td><a class="externalLink"
href="https://www.apache.org/licenses/LICENSE-2.0.txt";>Apache-2.0</a></td></tr>
<tr class="b">
<td align="left">org.apache.plc4x.plugins</td>
<td><a class="externalLink"
href="https://www.apache.org/plc4x-code-generation/plc4x-code-generation-protocol-base/";>plc4x-code-generation-protocol-base</a></td>
-<td>1.7.0-SNAPSHOT</td>
+<td>1.7.0</td>
<td>-</td>
<td>jar</td>
<td><a class="externalLink"
href="https://www.apache.org/licenses/LICENSE-2.0.txt";>Apache-2.0</a></td></tr>
<tr class="a">
<td align="left">org.apache.plc4x.plugins</td>
<td><a class="externalLink"
href="https://www.apache.org/plc4x-code-generation/plc4x-code-generation-types-base/";>plc4x-code-generation-types-base</a></td>
-<td>1.7.0-SNAPSHOT</td>
+<td>1.7.0</td>
<td>-</td>
<td>jar</td>
<td><a class="externalLink"
href="https://www.apache.org/licenses/LICENSE-2.0.txt";>Apache-2.0</a></td></tr>
diff --git a/developers/release/build-tools.html
b/developers/release/build-tools.html
index be1fbbf9a..e26f4404a 100644
--- a/developers/release/build-tools.html
+++ b/developers/release/build-tools.html
@@ -266,7 +266,7 @@ So please check <a href="release.html">here</a> (Chapters:
<code>Preparing your
<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>1.7.0-SNAPSHOT</code>, we create a branch <code>release/1.7</code>.</p>
+<p>So if currently the project version in develop is
<code>1.8.0-SNAPSHOT</code>, we create a branch <code>release/1.8</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>
@@ -285,11 +285,11 @@ This is the version the <code>develop</code> branch will
be changed to.</p>
</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>1.7.0</code> the command
would be the following:</p>
+So in case of preparing the release branch for <code>1.8.0</code> the command
would be the following:</p>
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -DbranchName=releases/code-generation/1.7</pre>
+<pre> mvn release:branch -DbranchName=releases/code-generation/1.8</pre>
</div>
</div>
<div class="paragraph">
@@ -297,7 +297,7 @@ So in case of preparing the release branch for
<code>1.7.0</code> the command wo
</div>
<div class="listingblock">
<div class="content">
-<pre> What is the new working copy version for "PLC4X Build Tools: Code
Generation"? (org.apache.plc4x.plugins:plc4x-code-generation) 1.7.1-SNAPSHOT: :
1.8.0-SNAPSHOT</pre>
+<pre> What is the new working copy version for "PLC4X Build Tools: Code
Generation"? (org.apache.plc4x.plugins:plc4x-code-generation) 1.8.1-SNAPSHOT: :
1.9.0-SNAPSHOT</pre>
</div>
</div>
<div class="paragraph">
@@ -307,7 +307,7 @@ So in case of preparing the release branch for
<code>1.7.0</code> the command wo
<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>releases/code-generation/1.7</code> branch is
created.</p>
+<p>However in the end the versions of the <code>develop</code> branch are
updated and a new <code>releases/code-generation/1.8</code> branch is
created.</p>
</div>
</div>
<div class="sect2">
@@ -321,7 +321,7 @@ So in case of preparing the release branch for
<code>1.7.0</code> the command wo
<div class="listingblock">
<div class="content">
<pre>==============================================================
-(Unreleased) Apache PLC4X 1.8.0-SNAPSHOT
+(Unreleased) Apache PLC4X 1.9.0-SNAPSHOT
==============================================================
New Features
@@ -421,7 +421,7 @@ Again, just in case you missed the first warning: Be sure
to ensure you have swi
<p>The version we want to release as (It will suggest the version you get by
omitting the <code>-SNAPSHOT</code> suffix, keep it as it is)</p>
</li>
<li>
-<p>The name of the tag the release commit will be tagged with in the SCM (Name
it <code>releases/code-generation/{release-version}</code>
(<code>releases/code-generation/1.7.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>releases/code-generation/{release-version}</code>
(<code>releases/code-generation/1.8.0</code> in our case)</p>
</li>
<li>
<p>The next development version (The version present in the pom after the
release) (leave it as it is suggested by the plugin)</p>
@@ -449,7 +449,7 @@ Again, just in case you missed the first warning: Be sure
to ensure you have swi
<p>Run a build with all tests</p>
</li>
<li>
-<p>Commit the changes (commit message: <code>[maven-release-plugin] prepare
release releases/code-generation/1.7.0</code>)</p>
+<p>Commit the changes (commit message: <code>[maven-release-plugin] prepare
release releases/code-generation/1.8.0</code>)</p>
</li>
<li>
<p>Push the commit</p>
@@ -481,7 +481,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 releases/code-generation/1.7.0" is tagged with the release tag
(in this case releases/code-generation/1.7.0)</p>
+<p>It is important that the commit with the message "[maven-release-plugin]
prepare release releases/code-generation/1.8.0" is tagged with the release tag
(in this case releases/code-generation/1.8.0)</p>
</div>
<div class="paragraph">
<p>If you check the commit itself, it should mainly consist of version updates
like this:</p>
@@ -503,7 +503,7 @@ is in the correct state. Please select the release branch
and verify the commit
</div>
</div>
<div class="paragraph">
-<p>This now updates the versions again, but this time from the release version
to the one we selected for the next development iteration (in this case
<code>1.7.1-SNAPSHOT</code>)</p>
+<p>This now updates the versions again, but this time from the release version
to the one we selected for the next development iteration (in this case
<code>1.8.1-SNAPSHOT</code>)</p>
</div>
<div class="admonitionblock note">
<table>
@@ -610,21 +610,21 @@ Here it automatically executes a maven build (You
don’t have to do this, i
<div class="listingblock">
<div class="content">
<pre> ./KEYS
- ./build-tools/code-generation/1.7.0
- ./build-tools/code-generation/1.7.0/rc1
- ./build-tools/code-generation/1.7.0/rc1/README
- ./build-tools/code-generation/1.7.0/rc1/RELEASE_NOTES
-
./build-tools/code-generation/1.7.0/rc1/apache-plc4x-code-generation-1.7.0-source-release.zip
-
./build-tools/code-generation/1.7.0/rc1/apache-plc4x-code-generation-1.7.0-source-release.zip.asc
-
./build-tools/code-generation/1.7.0/rc1/apache-plc4x-code-generation-1.7.0-source-release.zip.sha512</pre>
+ ./build-tools/code-generation/1.8.0
+ ./build-tools/code-generation/1.8.0/rc1
+ ./build-tools/code-generation/1.8.0/rc1/README
+ ./build-tools/code-generation/1.8.0/rc1/RELEASE_NOTES
+
./build-tools/code-generation/1.8.0/rc1/apache-plc4x-code-generation-1.8.0-source-release.zip
+
./build-tools/code-generation/1.8.0/rc1/apache-plc4x-code-generation-1.8.0-source-release.zip.asc
+
./build-tools/code-generation/1.8.0/rc1/apache-plc4x-code-generation-1.8.0-source-release.zip.sha512</pre>
</div>
</div>
<div class="paragraph">
-<p>I usually prepare exactly the same directory structure, starting with the
1.7.0 locally and then just import everything using the following command:</p>
+<p>I usually prepare exactly the same directory structure, starting with the
1.8.0 locally and then just import everything using the following command:</p>
</div>
<div class="listingblock">
<div class="content">
-<pre>svn import 1.7.0
https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.7.0
-m"Staging of rc1 of PLC4X Build-Tools (Code-Generation) 1.7.0"</pre>
+<pre>svn import 1.8.0
https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.8.0
-m"Staging of rc1 of PLC4X Build-Tools (Code-Generation) 1.8.0"</pre>
</div>
</div>
<div class="paragraph">
@@ -658,10 +658,10 @@ 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 Build-Tools Code-Generation 1.7.0 RC1
+ [VOTE] Apache PLC4X Build-Tools Code-Generation 1.8.0 RC1
Message:
- Apache PLC4X Build-Tools Code-Generation 1.7.0 has been staged under [2]
+ Apache PLC4X Build-Tools Code-Generation 1.8.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.
@@ -670,7 +670,7 @@ The following would be the one used to do our first TLP
release:</p>
are required to pass.
Repository: https://gitbox.apache.org/repos/asf/plc4x-build-tools.git
- Release tag: releases/code-generation/1.7.0
+ Release tag: releases/code-generation/1.8.0
Hash for the release tag: {replacethiswiththerealgitcommittag}
Per [3] "Before voting +1 PMC members are required to download
@@ -686,7 +686,7 @@ The following would be the one used to do our first TLP
release:</p>
[1]
https://repository.apache.org/content/repositories/orgapacheplc4x-{somefourdigitnumber}
- [2]
https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.7.0/rc1/
+ [2]
https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.8.0/rc1/
[3] https://www.apache.org/dev/release/validation.html#approving-a-release
[4] https://plc4x.apache.org/developers/release/validation.html</pre>
</div>
@@ -697,7 +697,7 @@ The following would be the one used to do our first TLP
release:</p>
<div class="listingblock">
<div class="content">
<pre> E-Mail Topic:
- [DISCUSS] Apache PLC4X Build-Tools Code-Generation 1.7.0 RC1
+ [DISCUSS] Apache PLC4X Build-Tools Code-Generation 1.8.0 RC1
Message:
This is the discussion thread for the corresponding VOTE thread.
@@ -722,7 +722,7 @@ The following would be the one used to do our first TLP
release:</p>
<div class="listingblock">
<div class="content">
<pre> E-Mail Topic:
- [RESULT] [VOTE] Apache PLC4X Build-Tools Code-Generation 1.7.0 RC1
+ [RESULT] [VOTE] Apache PLC4X Build-Tools Code-Generation 1.8.0 RC1
Message:
So, the vote passes with 3 +1 votes by PMC members and one +1 vote by a
non PMC member.
@@ -739,9 +739,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 1.7.0" \
-
https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.7.0/rc1
\
-
https://dist.apache.org/repos/dist/release/plc4x/build-tools/code-generation/1.7.0</pre>
+<pre> svn move -m "Release Apache PLC4X 1.8.0" \
+
https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/1.8.0/rc1
\
+
https://dist.apache.org/repos/dist/release/plc4x/build-tools/code-generation/1.8.0</pre>
</div>
</div>
<div class="paragraph">
@@ -792,7 +792,7 @@ This has to be done with git</p>
<div class="listingblock">
<div class="content">
<pre>git checkout release
-git merge releases/code-generation/1.7.0</pre>
+git merge releases/code-generation/1.8.0</pre>
</div>
</div>
<div class="paragraph">
@@ -800,7 +800,7 @@ git merge releases/code-generation/1.7.0</pre>
</div>
<div class="listingblock">
<div class="content">
-<pre>git merge -X theirs releases/code-generation/1.7.0</pre>
+<pre>git merge -X theirs releases/code-generation/1.8.0</pre>
</div>
</div>
<div class="paragraph">
diff --git a/plugin-management.html b/plugin-management.html
index ec1c743fc..b21a76eeb 100644
--- a/plugin-management.html
+++ b/plugin-management.html
@@ -275,7 +275,7 @@
<tr class="b">
<td align="left">org.apache.plc4x.plugins</td>
<td><a class="externalLink"
href="https://www.apache.org/plc4x-code-generation/plc4x-maven-plugin/";>plc4x-maven-plugin</a></td>
-<td>1.7.0-SNAPSHOT</td></tr>
+<td>1.7.0</td></tr>
<tr class="a">
<td align="left">org.apache.rat</td>
<td><a class="externalLink"
href="https://creadur.apache.org/rat/apache-rat-plugin/";>apache-rat-plugin</a></td>
