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 edde961 Site checkin for project PLC4X: Jenkins Tools
edde961 is described below
commit edde961bb89528109390ed1ef7171d2615a0264a
Author: jenkins <[email protected]>
AuthorDate: Fri May 15 15:27:40 2020 +0000
Site checkin for project PLC4X: Jenkins Tools
---
dependency-info.html | 14 +++----
dependency-management.html | 4 +-
developers/release/build-tools.html | 60 ++++++++++++++---------------
developers/release/release.html | 76 +++++++++++++++++++++----------------
developers/release/validation.html | 6 +--
plugin-management.html | 2 +-
scm.html | 4 +-
summary.html | 2 +-
8 files changed, 90 insertions(+), 78 deletions(-)
diff --git a/dependency-info.html b/dependency-info.html
index eba3808..70f364d 100644
--- a/dependency-info.html
+++ b/dependency-info.html
@@ -119,31 +119,31 @@
<pre><dependency>
<groupId>org.apache.plc4x</groupId>
<artifactId>plc4x-parent</artifactId>
- <version>0.7.0-SNAPSHOT</version>
+ <version>0.8.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.7.0-SNAPSHOT'</pre></div></section><section>
+<pre>'org.apache.plc4x:plc4x-parent:pom:0.8.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.7.0-SNAPSHOT">
+<pre><dependency org="org.apache.plc4x"
name="plc4x-parent" rev="0.8.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.7.0-SNAPSHOT')
+@Grab(group='org.apache.plc4x', module='plc4x-parent',
version='0.8.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.7.0-SNAPSHOT'</pre></div></section><section>
+<pre>compile
'org.apache.plc4x:plc4x-parent:0.8.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.7.0-SNAPSHOT"</pre></div></section><section>
+<pre>libraryDependencies += "org.apache.plc4x" %
"plc4x-parent" %
"0.8.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.7.0-SNAPSHOT"]</pre></div></section></section>
+<pre>[org.apache.plc4x/plc4x-parent
"0.8.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/dependency-management.html b/dependency-management.html
index 259e37f..60c4928 100644
--- a/dependency-management.html
+++ b/dependency-management.html
@@ -372,7 +372,7 @@
<tr class="a">
<td>org.antlr</td>
<td><a class="externalLink"
href="http://www.antlr.org/antlr4-runtime";>antlr4-runtime</a></td>
-<td>4.7.2</td>
+<td>4.8</td>
<td>jar</td>
<td><a class="externalLink" href="http://www.antlr.org/license.html";>The BSD
License</a></td></tr>
<tr class="b">
@@ -774,7 +774,7 @@
<tr class="b">
<td>org.yaml</td>
<td><a class="externalLink" href="http://www.snakeyaml.org";>snakeyaml</a></td>
-<td>1.23</td>
+<td>1.24</td>
<td>jar</td>
<td><a class="externalLink"
href="http://www.apache.org/licenses/LICENSE-2.0.txt";>Apache License, Version
2.0</a></td></tr>
<tr class="a">
diff --git a/developers/release/build-tools.html
b/developers/release/build-tools.html
index 235f888..e7d70e4 100644
--- a/developers/release/build-tools.html
+++ b/developers/release/build-tools.html
@@ -243,7 +243,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>0.7.0-SNAPSHOT</code>, we create a branch <code>rel/0.7</code>.</p>
+<p>So if currently the project version in develop is
<code>0.8.0-SNAPSHOT</code>, we create a branch <code>rel/0.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>
@@ -266,7 +266,7 @@ So in case of preparing the release branch for
<code>{project.version}</code> th
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -DbranchName=rel/code-generation/0.7</pre>
+<pre> mvn release:branch -DbranchName=rel/code-generation/0.8</pre>
</div>
</div>
<div class="paragraph">
@@ -274,7 +274,7 @@ So in case of preparing the release branch for
<code>{project.version}</code> th
</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-generaton) 0.7.1-SNAPSHOT: :
0.8.0-SNAPSHOT</pre>
+<pre> What is the new working copy version for "PLC4X Build Tools: Code
Generation"? (org.apache.plc4x.plugins:plc4x-code-generaton) 0.8.1-SNAPSHOT: :
0.9.0-SNAPSHOT</pre>
</div>
</div>
<div class="paragraph">
@@ -284,7 +284,7 @@ So in case of preparing the release branch for
<code>{project.version}</code> th
<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/code-generation/0.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>rel/code-generation/0.8</code> branch is created.</p>
</div>
</div>
<div class="sect2">
@@ -298,7 +298,7 @@ So in case of preparing the release branch for
<code>{project.version}</code> th
<div class="listingblock">
<div class="content">
<pre>==============================================================
-(Unreleased) Apache PLC4X 0.8.0-SNAPSHOT
+(Unreleased) Apache PLC4X 0.9.0-SNAPSHOT
==============================================================
New Features
@@ -371,10 +371,10 @@ In order to prepare a release-candidate, the first step
is switching to the corr
<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/code-generation/{release-version}</code>
(<code>release/code-generation/0.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>release/code-generation/{release-version}</code>
(<code>release/code-generation/0.8.0</code> in our case)</p>
</li>
<li>
-<p>The next development version (The version present in the pom after the
release) (<code>0.8.0</code> in our case)</p>
+<p>The next development version (The version present in the pom after the
release) (<code>0.9.0</code> in our case)</p>
</li>
</ol>
</div>
@@ -399,7 +399,7 @@ In order to prepare a release-candidate, the first step is
switching to the corr
<p>Run a build with all tests</p>
</li>
<li>
-<p>Commit the changes (commit message: <code>[maven-release-plugin] prepare
release release/code-generation/0.7.0</code>)</p>
+<p>Commit the changes (commit message: <code>[maven-release-plugin] prepare
release release/code-generation/0.8.0</code>)</p>
</li>
<li>
<p>Push the commit</p>
@@ -431,7 +431,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/code-generation/0.7.0" is tagged with the release tag
(in this case release/code-generation/0.7.0)</p>
+<p>It is important that the commit with the message "[maven-release-plugin]
prepare release release/code-generation/0.8.0" is tagged with the release tag
(in this case release/code-generation/0.8.0)</p>
</div>
<div class="paragraph">
<p>If you check the commit itself, it should mainly consist of version updates
like this:</p>
@@ -453,7 +453,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>0.8.0-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>0.9.0-SNAPSHOT</code>)</p>
</div>
<div class="admonitionblock note">
<table>
@@ -560,13 +560,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.7.0/build-tools/code-generation
- ./0.7.0/build-tools/code-generation/rc1
- ./0.7.0/build-tools/code-generation/rc1/README
- ./0.7.0/build-tools/code-generation/rc1/RELEASE_NOTES
-
./0.7.0/build-tools/code-generation/rc1/apache-plc4x-code-generation-0.7.0-source-release.zip
-
./0.7.0/build-tools/code-generation/rc1/apache-plc4x-code-generation-0.7.0-source-release.zip.asc
-
./0.7.0/build-tools/code-generation/rc1/apache-plc4x-code-generation-0.7.0-source-release.zip.sha512</pre>
+ ./0.8.0/build-tools/code-generation
+ ./0.8.0/build-tools/code-generation/rc1
+ ./0.8.0/build-tools/code-generation/rc1/README
+ ./0.8.0/build-tools/code-generation/rc1/RELEASE_NOTES
+
./0.8.0/build-tools/code-generation/rc1/apache-plc4x-code-generation-0.8.0-source-release.zip
+
./0.8.0/build-tools/code-generation/rc1/apache-plc4x-code-generation-0.8.0-source-release.zip.asc
+
./0.8.0/build-tools/code-generation/rc1/apache-plc4x-code-generation-0.8.0-source-release.zip.sha512</pre>
</div>
</div>
<div class="paragraph">
@@ -603,7 +603,7 @@ The following would be the one used to do our first TLP
release:</p>
[VOTE] Apache PLC4X Build-Tools Code-Generation {current-full-version RC1
Message:
- Apache PLC4X Build-Tools Code-Generation 0.7.0 has been staged under [2]
+ Apache PLC4X Build-Tools Code-Generation 0.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.
@@ -612,7 +612,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: release/code-generation/0.7.0
+ Release tag: release/code-generation/0.8.0
Hash for the release tag: {replacethiswiththerealgitcommittag}
Per [3] "Before voting +1 PMC members are required to download
@@ -628,7 +628,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/0.7.0/rc1/
+ [2]
https://dist.apache.org/repos/dist/dev/plc4x/build-tools/code-generation/0.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>
@@ -639,7 +639,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 0.7.0 RC1
+ [DISCUSS] Apache PLC4X 0.8.0 RC1
Message:
This is the discussion thread for the corresponding VOTE thread.
@@ -664,7 +664,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 0.7.0 RC1
+ [RESULT] [VOTE] Apache PLC4X 0.8.0 RC1
Message:
So, the vote passes with 3 +1 votes by PMC members and one +1 vote by a
non PMC member.
@@ -681,9 +681,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.7.0" \
- https://dist.apache.org/repos/dist/dev/plc4x/0.7.0/rc1 \
- https://dist.apache.org/repos/dist/release/plc4x/0.7.0</pre>
+<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>
</div>
</div>
<div class="paragraph">
@@ -734,7 +734,7 @@ This has to be done with git</p>
<div class="listingblock">
<div class="content">
<pre>git checkout master
-git merge release/0.7.0</pre>
+git merge release/0.8.0</pre>
</div>
</div>
<div class="paragraph">
@@ -742,7 +742,7 @@ git merge release/0.7.0</pre>
</div>
<div class="listingblock">
<div class="content">
-<pre>git merge -X theirs release/0.7.0</pre>
+<pre>git merge -X theirs release/0.8.0</pre>
</div>
</div>
<div class="paragraph">
@@ -776,7 +776,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.7.0/apache-plc4x-0.7.0-source-release.zip";
class="bare">http://archive.apache.org/dist/plc4x/0.7.0/apache-plc4x-0.7.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.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>
</li>
<li>
<p>Add the new Release under <em>Current Releases</em> and change all links.
@@ -809,10 +809,10 @@ [email protected]
[email protected]
E-Mail Topic:
-[ANNOUNCE] Apache PLC4X 0.7.0 released
+[ANNOUNCE] Apache PLC4X 0.8.0 released
Message:
-The Apache PLC4X team is pleased to announce the release of Apache PLC4X 0.7.0
+The Apache PLC4X team is pleased to announce the release of Apache PLC4X 0.8.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/release.html b/developers/release/release.html
index 7ad13bd..92ed057 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -387,6 +387,18 @@ He can then sign your key and hereby enable you to sign
Apache release artifacts
</profile></pre>
</div>
</div>
+<div class="paragraph">
+<p>Currently there is a Java-Version sweet-spot for being able to release all
modules and that is Java 11.</p>
+</div>
+<div class="paragraph">
+<p>So be sure to set <code>Java 11</code> as the java version used to do the
release.</p>
+</div>
+<div class="paragraph">
+<p>Also at least <code>Maven 3.6</code> is required for CMake.</p>
+</div>
+<div class="paragraph">
+<p>Ideally use the Maven-Wrapper to ensure the Maven version fits the
build.</p>
+</div>
</div>
<div class="sect2">
<h3 id="preparing_the_codebase_for_a_release">Preparing the codebase for a
release</h3>
@@ -409,7 +421,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.7.0-SNAPSHOT</code>, we create a branch <code>rel/0.7</code>.</p>
+<p>So if currently the project version in develop is
<code>0.8.0-SNAPSHOT</code>, we create a branch <code>rel/0.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>
@@ -427,16 +439,16 @@ Otherwise the non-default modules on develop will
reference the old version whic
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:branch -P
with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash
-DbranchName=rel/{minor-version}</pre>
+<pre>mvn release:branch -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-logstash,with-proxies,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.7.0-SNAPSHOT</code> the
command would be the following:</p>
+So in case of preparing the release branch for <code>0.8.0-SNAPSHOT</code> the
command would be the following:</p>
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:branch -P
with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash
-DbranchName=rel/0.7</pre>
+<pre> mvn release:branch -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-logstash,with-proxies,with-python,with-sandbox
-DbranchName=rel/0.8</pre>
</div>
</div>
<div class="paragraph">
@@ -444,7 +456,7 @@ So in case of preparing the release branch for
<code>0.7.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.7.1-SNAPSHOT: : 0.8.0-SNAPSHOT</pre>
+<pre> What is the new working copy version for "PLC4X"?
(org.apache.plc4x:plc4x-parent) 0.8.1-SNAPSHOT: : 0.9.0-SNAPSHOT</pre>
</div>
</div>
<div class="paragraph">
@@ -454,7 +466,7 @@ So in case of preparing the release branch for
<code>0.7.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>rel/0.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>rel/0.8</code> branch is created.</p>
</div>
</div>
<div class="sect2">
@@ -468,7 +480,7 @@ So in case of preparing the release branch for
<code>0.7.0-SNAPSHOT</code> the c
<div class="listingblock">
<div class="content">
<pre>==============================================================
-(Unreleased) Apache PLC4X 0.8.0-SNAPSHOT
+(Unreleased) Apache PLC4X 0.9.0-SNAPSHOT
==============================================================
New Features
@@ -528,7 +540,7 @@ 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-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash</pre>
+<pre>mvn release:prepare -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-logstash,with-proxies,with-python,with-sandbox</pre>
</div>
</div>
<div class="paragraph">
@@ -541,7 +553,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.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>release/{release-version}</code> (<code>release/0.8.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>
@@ -566,7 +578,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.7.0</code>)</p>
+<p>Commit the changes (commit message: <code>[maven-release-plugin] prepare
release release/0.8.0</code>)</p>
</li>
<li>
<p>Push the commit</p>
@@ -598,7 +610,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.7.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 release/0.8.0" is tagged with the release tag (in this case
release/0.3.0)</p>
</div>
<div class="paragraph">
<p>If you check the commit itself, it should mainly consist of version updates
like this:</p>
@@ -730,13 +742,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.7.0/
- ./0.7.0/rc1
- ./0.7.0/rc1/README
- ./0.7.0/rc1/RELEASE_NOTES
- ./0.7.0/rc1/apache-plc4x-0.7.0-source-release.zip
- ./0.7.0/rc1/apache-plc4x-0.7.0-source-release.zip.asc
- ./0.7.0/rc1/apache-plc4x-0.7.0-source-release.zip.sha512</pre>
+ ./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>
</div>
</div>
<div class="paragraph">
@@ -779,17 +791,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.7.0 RC1
+[VOTE] Apache PLC4X 0.8.0 RC1
Message:
-Apache PLC4X 0.7.0 has been staged under [2] and it’s time to vote
+Apache PLC4X 0.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.
A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.
-Release tag: release/0.7.0
+Release tag: release/0.8.0
Hash for the release tag: {replacethiswiththerealgitcommittag}
Per [3] "Before voting +1 PMC members are required to download
@@ -805,7 +817,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.7.0/rc1
+[2] https://dist.apache.org/repos/dist/dev/plc4x/0.8.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>
@@ -816,7 +828,7 @@ You can achieve the above by following [4].
<div class="listingblock">
<div class="content">
<pre>E-Mail Topic:
-[DISCUSS] Apache PLC4X 0.7.0 RC1
+[DISCUSS] Apache PLC4X 0.8.0 RC1
Message:
This is the discussion thread for the corresponding VOTE thread.
@@ -841,7 +853,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.7.0 RC1
+[RESULT] [VOTE] Apache PLC4X 0.8.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>
@@ -856,9 +868,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.7.0" \
- https://dist.apache.org/repos/dist/dev/plc4x/0.7.0/rc1 \
- https://dist.apache.org/repos/dist/release/plc4x/0.7.0</pre>
+<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>
</div>
</div>
<div class="paragraph">
@@ -929,7 +941,7 @@ This has to be done with git</p>
<div class="listingblock">
<div class="content">
<pre>git checkout master
-git merge release/0.7.0</pre>
+git merge release/0.8.0</pre>
</div>
</div>
<div class="paragraph">
@@ -937,7 +949,7 @@ git merge release/0.7.0</pre>
</div>
<div class="listingblock">
<div class="content">
-<pre>git merge -X theirs release/0.7.0</pre>
+<pre>git merge -X theirs release/0.8.0</pre>
</div>
</div>
<div class="paragraph">
@@ -971,7 +983,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.7.0/apache-plc4x-0.7.0-source-release.zip";
class="bare">http://archive.apache.org/dist/plc4x/0.7.0/apache-plc4x-0.7.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.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>
</li>
<li>
<p>Add the new Release under <em>Current Releases</em> and change all links.
@@ -1004,10 +1016,10 @@ CC:
[email protected]
E-Mail Topic:
-[ANNOUNCE] Apache PLC4X 0.7.0 released
+[ANNOUNCE] Apache PLC4X 0.8.0 released
Message:
-The Apache PLC4X team is pleased to announce the release of Apache PLC4X 0.7.0
+The Apache PLC4X team is pleased to announce the release of Apache PLC4X 0.8.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 1348952..2659288 100644
--- a/developers/release/validation.html
+++ b/developers/release/validation.html
@@ -357,7 +357,7 @@ gsha512sum -c
apache-plc4x-{current-full-version}-source-release.zip.sha512</pre
</div>
<div class="listingblock">
<div class="content">
-<pre>java -jar apache-rat-0.13.jar apache-plc4x-0.7.0-source-release.zip >
rat.log</pre>
+<pre>java -jar apache-rat-0.13.jar apache-plc4x-0.8.0-source-release.zip >
rat.log</pre>
</div>
</div>
<div class="paragraph">
@@ -374,11 +374,11 @@ gsha512sum -c
apache-plc4x-{current-full-version}-source-release.zip.sha512</pre
</div>
<div class="listingblock">
<div class="content">
-<pre>tools/download_staged_release.sh 0.7.0 1</pre>
+<pre>tools/download_staged_release.sh 0.8.0 1</pre>
</div>
</div>
<div class="paragraph">
-<p>This will download all the files into a directory:
<code>downloaded-plc4x-0.7.01</code>.</p>
+<p>This will download all the files into a directory:
<code>downloaded-plc4x-0.8.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/plugin-management.html b/plugin-management.html
index 86d61ba..7cbc5d7 100644
--- a/plugin-management.html
+++ b/plugin-management.html
@@ -134,7 +134,7 @@
<tr class="a">
<td>org.antlr</td>
<td><a class="externalLink"
href="http://www.antlr.org/antlr4-maven-plugin";>antlr4-maven-plugin</a></td>
-<td>4.7.2</td></tr>
+<td>4.8</td></tr>
<tr class="b">
<td>org.apache.felix</td>
<td><a class="externalLink"
href="http://felix.apache.org/components/bundle-plugin/";>maven-bundle-plugin</a></td>
diff --git a/scm.html b/scm.html
index 3cb5a89..107e20c 100644
--- a/scm.html
+++ b/scm.html
@@ -122,11 +122,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 --branch rel/0.7
https://gitbox.apache.org/repos/asf/plc4x.git</pre></div></section><section>
+<pre>$ git clone
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 --branch rel/0.7
https://gitbox.apache.org/repos/asf/plc4x.git</pre></div></section><section>
+<pre>$ git clone
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 1386217..f84114f 100644
--- a/summary.html
+++ b/summary.html
@@ -153,7 +153,7 @@
<td>plc4x-parent</td></tr>
<tr class="b">
<td>Version</td>
-<td>0.7.0-SNAPSHOT</td></tr>
+<td>0.8.0-SNAPSHOT</td></tr>
<tr class="a">
<td>Type</td>
<td>pom</td></tr></table></section></section>
