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 e057c11 Site checkin for project PLC4X: Jenkins Tools
e057c11 is described below
commit e057c1156f2596d12378fac3c36666bb8378820b
Author: jenkins <[email protected]>
AuthorDate: Mon Jul 6 15:02:01 2020 +0000
Site checkin for project PLC4X: Jenkins Tools
---
developers/release/build-tools.html | 8 ++++----
developers/release/release.html | 10 +++++-----
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/developers/release/build-tools.html
b/developers/release/build-tools.html
index f1c8c6b..dd54a94 100644
--- a/developers/release/build-tools.html
+++ b/developers/release/build-tools.html
@@ -245,7 +245,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.8.0-SNAPSHOT</code>, we create a branch <code>rel/0.8</code>.</p>
+<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>
</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>
@@ -259,7 +259,7 @@ This is the version the <code>develop</code> branch will be
changed to.</p>
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:branch -DbranchName=rel/code-generation/{minor-version}</pre>
+<pre>mvn release:branch
-DbranchName=release/code-generation/{minor-version}</pre>
</div>
</div>
<div class="paragraph">
@@ -268,7 +268,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.8</pre>
+<pre> mvn release:branch -DbranchName=release/code-generation/0.8</pre>
</div>
</div>
<div class="paragraph">
@@ -286,7 +286,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.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>release/code-generation/0.8</code> branch is
created.</p>
</div>
</div>
<div class="sect2">
diff --git a/developers/release/release.html b/developers/release/release.html
index 0075e1c..4d532e5 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -249,7 +249,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-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash
-DbranchName=rel/{current-short-version}</pre>
+<pre> mvn release:branch -P
with-sandbox,with-cpp,with-boost,with-dotnet,with-python,with-proxies,with-logstash
-DbranchName=release/{current-short-version}</pre>
</div>
</div>
<div class="ulist checklist">
@@ -423,7 +423,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>rel/0.8</code>.</p>
+<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>
</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>
@@ -441,7 +441,7 @@ 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-boost,with-c,with-cpp,with-docker,with-dotnet,with-logstash,with-proxies,with-python,with-sandbox
-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=release/{minor-version}</pre>
</div>
</div>
<div class="paragraph">
@@ -450,7 +450,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> 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>
+<pre> mvn release:branch -P
with-boost,with-c,with-cpp,with-docker,with-dotnet,with-logstash,with-proxies,with-python,with-sandbox
-DbranchName=release/0.8</pre>
</div>
</div>
<div class="paragraph">
@@ -468,7 +468,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>rel/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>release/0.8</code> branch is created.</p>
</div>
</div>
<div class="sect2">
