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 c6d4fec Site checkin for project PLC4X: Jenkins Tools
c6d4fec is described below
commit c6d4fec83ac48ffedf9abaf71f597ffc99f480f0
Author: jenkins <[email protected]>
AuthorDate: Mon Jan 25 12:13:49 2021 +0000
Site checkin for project PLC4X: Jenkins Tools
---
dependency-info.html | 14 ++++----
developers/release/release.html | 66 +++++++++++++++++++-------------------
developers/release/validation.html | 6 ++--
scm.html | 4 +--
summary.html | 2 +-
5 files changed, 46 insertions(+), 46 deletions(-)
diff --git a/dependency-info.html b/dependency-info.html
index c553db0..038d0f4 100644
--- a/dependency-info.html
+++ b/dependency-info.html
@@ -123,31 +123,31 @@
<pre><dependency>
<groupId>org.apache.plc4x</groupId>
<artifactId>plc4x-parent</artifactId>
- <version>0.8.0-SNAPSHOT</version>
+ <version>0.9.0-SNAPSHOT</version>
<type>pom</type>
</dependency></pre></div></section><section>
<h3><a name="Apache_Buildr"></a>Apache Buildr</h3><a name="Apache_Buildr"></a>
<div class="source">
-<pre>'org.apache.plc4x:plc4x-parent:pom:0.8.0-SNAPSHOT'</pre></div></section><section>
+<pre>'org.apache.plc4x:plc4x-parent:pom:0.9.0-SNAPSHOT'</pre></div></section><section>
<h3><a name="Apache_Ivy"></a>Apache Ivy</h3><a name="Apache_Ivy"></a>
<div class="source">
-<pre><dependency org="org.apache.plc4x"
name="plc4x-parent" rev="0.8.0-SNAPSHOT">
+<pre><dependency org="org.apache.plc4x"
name="plc4x-parent" rev="0.9.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 class="source">
<pre>@Grapes(
-@Grab(group='org.apache.plc4x', module='plc4x-parent',
version='0.8.0-SNAPSHOT')
+@Grab(group='org.apache.plc4x', module='plc4x-parent',
version='0.9.0-SNAPSHOT')
)</pre></div></section><section>
<h3><a name="Gradle.2FGrails"></a>Gradle/Grails</h3><a
name="Gradle.2FGrails"></a>
<div class="source">
-<pre>compile
'org.apache.plc4x:plc4x-parent:0.8.0-SNAPSHOT'</pre></div></section><section>
+<pre>compile
'org.apache.plc4x:plc4x-parent:0.9.0-SNAPSHOT'</pre></div></section><section>
<h3><a name="Scala_SBT"></a>Scala SBT</h3><a name="Scala_SBT"></a>
<div class="source">
-<pre>libraryDependencies += "org.apache.plc4x" %
"plc4x-parent" %
"0.8.0-SNAPSHOT"</pre></div></section><section>
+<pre>libraryDependencies += "org.apache.plc4x" %
"plc4x-parent" %
"0.9.0-SNAPSHOT"</pre></div></section><section>
<h3><a name="Leiningen"></a>Leiningen</h3><a name="Leiningen"></a>
<div class="source">
-<pre>[org.apache.plc4x/plc4x-parent
"0.8.0-SNAPSHOT"]</pre></div></section></section>
+<pre>[org.apache.plc4x/plc4x-parent
"0.9.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 50a89c1..880cabf 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -251,7 +251,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-logstash,with-python,with-sandbox
-DbranchName=release/{current-short-version}</pre>
+<pre> mvn release:branch -P
with-boost,with-c,with-docker,with-dotnet,with-go,with-logstash,with-python,with-sandbox
-DbranchName=rel/{current-short-version}</pre>
</div>
</div>
<div class="ulist checklist">
@@ -449,7 +449,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.8.0-SNAPSHOT</code>, we create a branch <code>release/0.8</code>.</p>
+<p>So if currently the project version in develop is
<code>0.9.0-SNAPSHOT</code>, we create a branch <code>release/0.9</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>
@@ -467,16 +467,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-boost,with-c,with-docker,with-dotnet,with-logstash,with-python,with-sandbox
-DbranchName=release/{minor-version}</pre>
+<pre>mvn release:branch -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-go,with-logstash,with-python,with-sandbox
-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.8.0-SNAPSHOT</code> the
command would be the following:</p>
+So in case of preparing the release branch for <code>0.9.0-SNAPSHOT</code> the
command would be the following:</p>
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P
with-boost,with-c,with-docker,with-dotnet,with-logstash,with-python,with-sandbox
-DbranchName=release/0.8</pre>
+<pre> mvn release:branch -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-go,with-logstash,with-python,with-sandbox
-DbranchName=rel/0.9</pre>
</div>
</div>
<div class="paragraph">
@@ -484,7 +484,7 @@ So in case of preparing the release branch for
<code>0.8.0-SNAPSHOT</code> the c
</div>
<div class="listingblock">
<div class="content">
-<pre> What is the new working copy version for "PLC4X"?
(org.apache.plc4x:plc4x-parent) 0.8.1-SNAPSHOT: : 0.9.0-SNAPSHOT</pre>
+<pre> What is the new working copy version for "PLC4X"?
(org.apache.plc4x:plc4x-parent) 0.9.1-SNAPSHOT: : 0.10.0-SNAPSHOT</pre>
</div>
</div>
<div class="paragraph">
@@ -494,7 +494,7 @@ So in case of preparing the release branch for
<code>0.8.0-SNAPSHOT</code> the c
<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>release/0.8</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.9</code> branch is created.</p>
</div>
</div>
<div class="sect2">
@@ -508,7 +508,7 @@ So in case of preparing the release branch for
<code>0.8.0-SNAPSHOT</code> the c
<div class="listingblock">
<div class="content">
<pre>==============================================================
-(Unreleased) Apache PLC4X 0.9.0-SNAPSHOT
+(Unreleased) Apache PLC4X 0.10.0-SNAPSHOT
==============================================================
New Features
@@ -581,7 +581,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>release/{release-version}</code> (<code>release/0.8.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.9.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>
@@ -606,7 +606,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 release/0.8.0</code>)</p>
+<p>Commit the changes (commit message: <code>[maven-release-plugin] prepare
release v0.9.0</code>)</p>
</li>
<li>
<p>Push the commit</p>
@@ -638,7 +638,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 release/0.8.0" is tagged with the release tag (in this case
release/0.3.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.9.0)</p>
</div>
<div class="paragraph">
<p>If you check the commit itself, it should mainly consist of version updates
like this:</p>
@@ -770,13 +770,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.8.0/
- ./0.8.0/rc1
- ./0.8.0/rc1/README
- ./0.8.0/rc1/RELEASE_NOTES
- ./0.8.0/rc1/apache-plc4x-0.8.0-source-release.zip
- ./0.8.0/rc1/apache-plc4x-0.8.0-source-release.zip.asc
- ./0.8.0/rc1/apache-plc4x-0.8.0-source-release.zip.sha512</pre>
+ ./0.9.0/
+ ./0.9.0/rc1
+ ./0.9.0/rc1/README
+ ./0.9.0/rc1/RELEASE_NOTES
+ ./0.9.0/rc1/apache-plc4x-0.9.0-source-release.zip
+ ./0.9.0/rc1/apache-plc4x-0.9.0-source-release.zip.asc
+ ./0.9.0/rc1/apache-plc4x-0.9.0-source-release.zip.sha512</pre>
</div>
</div>
<div class="paragraph">
@@ -819,17 +819,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.8.0 RC1
+[VOTE] Apache PLC4X 0.9.0 RC1
Message:
-Apache PLC4X 0.8.0 has been staged under [2] and it’s time to vote
+Apache PLC4X 0.9.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: release/0.8.0
+Release tag: v0.9.0
Hash for the release tag: {replacethiswiththerealgitcommittag}
Per [3] "Before voting +1 PMC members are required to download
@@ -845,7 +845,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.8.0/rc1
+[2] https://dist.apache.org/repos/dist/dev/plc4x/0.9.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>
@@ -856,7 +856,7 @@ You can achieve the above by following [4].
<div class="listingblock">
<div class="content">
<pre>E-Mail Topic:
-[DISCUSS] Apache PLC4X 0.8.0 RC1
+[DISCUSS] Apache PLC4X 0.9.0 RC1
Message:
This is the discussion thread for the corresponding VOTE thread.
@@ -881,7 +881,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.8.0 RC1
+[RESULT] [VOTE] Apache PLC4X 0.9.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>
@@ -896,9 +896,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.8.0" \
- https://dist.apache.org/repos/dist/dev/plc4x/0.8.0/rc1 \
- https://dist.apache.org/repos/dist/release/plc4x/0.8.0</pre>
+<pre> svn move -m "Release Apache PLC4X 0.9.0" \
+ https://dist.apache.org/repos/dist/dev/plc4x/0.9.0/rc1 \
+ https://dist.apache.org/repos/dist/release/plc4x/0.9.0</pre>
</div>
</div>
<div class="paragraph">
@@ -918,7 +918,7 @@ This is done by moving them inside the Apache SVN.</p>
</div>
<div class="literalblock">
<div class="content">
-<pre>svn delete https://dist.apache.org/repos/dist/release/plc4x/0.3.0/
-m"deleted version 0.3.0"</pre>
+<pre>svn delete
https://dist.apache.org/repos/dist/release/plc4x/{current-full-version}/
-m"deleted version {current-full-version}"</pre>
</div>
</div>
<div class="paragraph">
@@ -969,7 +969,7 @@ This has to be done with git</p>
<div class="listingblock">
<div class="content">
<pre>git checkout release
-git merge release/0.8.0</pre>
+git merge release/0.9.0</pre>
</div>
</div>
<div class="paragraph">
@@ -977,7 +977,7 @@ git merge release/0.8.0</pre>
</div>
<div class="listingblock">
<div class="content">
-<pre>git merge -X theirs release/0.8.0</pre>
+<pre>git merge -X theirs release/0.9.0</pre>
</div>
</div>
<div class="paragraph">
@@ -1010,7 +1010,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.8.0/apache-plc4x-0.8.0-source-release.zip";
class="bare">http://archive.apache.org/dist/plc4x/0.8.0/apache-plc4x-0.8.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.9.0/apache-plc4x-0.9.0-source-release.zip";
class="bare">http://archive.apache.org/dist/plc4x/0.9.0/apache-plc4x-0.9.0-source-release.zip</a></code></p>
</li>
<li>
<p>Add the new Release under <em>Current Releases</em> and change all links.
@@ -1043,10 +1043,10 @@ CC:
[email protected]
E-Mail Topic:
-[ANNOUNCE] Apache PLC4X 0.8.0 released
+[ANNOUNCE] Apache PLC4X 0.9.0 released
Message:
-The Apache PLC4X team is pleased to announce the release of Apache PLC4X 0.8.0
+The Apache PLC4X team is pleased to announce the release of Apache PLC4X 0.9.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 5067d12..5291a74 100644
--- a/developers/release/validation.html
+++ b/developers/release/validation.html
@@ -372,7 +372,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.8.0-source-release.zip >
rat.log</pre>
+<pre>java -jar apache-rat-0.13.jar apache-plc4x-0.9.0-source-release.zip >
rat.log</pre>
</div>
</div>
<div class="paragraph">
@@ -389,11 +389,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.8.0 1</pre>
+<pre>tools/download_staged_release.sh 0.9.0 1</pre>
</div>
</div>
<div class="paragraph">
-<p>This will download all the files into a directory:
<code>downloaded-plc4x-0.8.01</code>.</p>
+<p>This will download all the files into a directory:
<code>downloaded-plc4x-0.9.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/scm.html b/scm.html
index cb81cbe..50b4293 100644
--- a/scm.html
+++ b/scm.html
@@ -126,11 +126,11 @@
<h2><a name="Anonymous_Access"></a>Anonymous Access</h2><a
name="Anonymous_Access"></a>
<p>The source can be checked out anonymously from Git with this command (See
<a class="externalLink"
href="https://git-scm.com/docs/git-clone";>https://git-scm.com/docs/git-clone</a>):</p>
<div class="source">
-<pre>$ git clone
https://gitbox.apache.org/repos/asf/plc4x.git</pre></div></section><section>
+<pre>$ git clone --branch release/0.8
https://gitbox.apache.org/repos/asf/plc4x.git</pre></div></section><section>
<h2><a name="Developer_Access"></a>Developer Access</h2><a
name="Developer_Access"></a>
<p>Only project developers can access the Git tree via this method (See <a
class="externalLink"
href="https://git-scm.com/docs/git-clone";>https://git-scm.com/docs/git-clone</a>).</p>
<div class="source">
-<pre>$ git clone
https://gitbox.apache.org/repos/asf/plc4x.git</pre></div></section><section>
+<pre>$ git clone --branch release/0.8
https://gitbox.apache.org/repos/asf/plc4x.git</pre></div></section><section>
<h2><a name="Access_from_Behind_a_Firewall"></a>Access from Behind a
Firewall</h2><a name="Access_from_Behind_a_Firewall"></a>
<p>Refer to the documentation of the SCM used for more information about
access behind a firewall.</p></section>
</main>
diff --git a/summary.html b/summary.html
index 9aea0b0..13bfed4 100644
--- a/summary.html
+++ b/summary.html
@@ -157,7 +157,7 @@
<td>plc4x-parent</td></tr>
<tr class="b">
<td>Version</td>
-<td>0.8.0-SNAPSHOT</td></tr>
+<td>0.9.0-SNAPSHOT</td></tr>
<tr class="a">
<td>Type</td>
<td>pom</td></tr></table></section></section>
