Site checkin for project PLC4X: Jenkins Tools
diff --git a/developers/release/release.html b/developers/release/release.html
index ebb3384..32284bd 100644
--- a/developers/release/release.html
+++ b/developers/release/release.html
@@ -282,7 +282,7 @@
</div>
<div class="listingblock">
<div class="content">
-<pre> mvn release:perform -DreleaseProfiles=apache-release</pre>
+<pre> mvn clean release:perform</pre>
</div>
</div>
<div class="ulist checklist">
@@ -689,13 +689,16 @@
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:rollback</pre>
+<pre>mvn release:rollback -P with-c,with-dotnet,with-go,with-python,with-sandbox</pre>
</div>
</div>
<div class="paragraph">
<p>It will change the versions back and commit and push things.</p>
</div>
<div class="paragraph">
+<p>Also, should you check if you have any uncommitted changes (as our code-generation can make git think they are "dirty")</p>
+</div>
+<div class="paragraph">
<p>However, it will not delete the tag in GIT (locally and remotely). So you have to do that manually or use a different tag next time.</p>
</div>
<div class="sect2">
@@ -705,9 +708,21 @@
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn release:perform</pre>
+<pre>mvn clean release:perform</pre>
</div>
</div>
+<div class="admonitionblock note">
+<table>
+<tr>
+<td class="icon">
+<i class="fa icon-note" title="Note"></i>
+</td>
+<td class="content">
+The clean is only for making sure there is no artifacts in <code>target</code> directly, but only in <code>target/checkout/target</code>.
+</td>
+</tr>
+</table>
+</div>
<div class="paragraph">
<p>This executes automatically as all information it requires is located in the <code>release.properties</code> file the <code>prepare</code>-goal prepared.</p>
</div>
@@ -717,7 +732,7 @@
</div>
<div class="literalblock">
<div class="content">
-<pre>mvn clean deploy -P apache-release</pre>
+<pre>mvn deploy -P apache-release</pre>
</div>
</div>
<div class="paragraph">
@@ -913,6 +928,60 @@
</div>
</div>
<div class="sect2">
+<h3 id="going_back_for_a_new_release_candidate">Going back for a new release candidate</h3>
+<div class="paragraph">
+<p>If however for some reason it is needed to prepare a new RC for the release. Please follow these steps:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<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>
+</div>
+</div>
+</li>
+<li>
+<p>Delete the tag locally:</p>
+<div class="literalblock">
+<div class="content">
+<pre>git tag -d v{current-full-version}</pre>
+</div>
+</div>
+</li>
+<li>
+<p>Delete the tag remotely:</p>
+<div class="literalblock">
+<div class="content">
+<pre>git push --delete origin v{current-full-version}</pre>
+</div>
+</div>
+</li>
+<li>
+<p>Commit all changes</p>
+</li>
+<li>
+<p>Drop the staging repo at <a href="https://repository.apache.org" class="bare">https://repository.apache.org</a></p>
+</li>
+<li>
+<p>Delete the previous RC in SVN</p>
+<div class="literalblock">
+<div class="content">
+<pre>svn rm https://dist.apache.org/repos/dist/dev/plc4x/0.9.0/rc1 -m"Removed rc1 of PLC4x 0.9.0"</pre>
+</div>
+</div>
+</li>
+<li>
+<p>Reply to the <code>VOTE</code> and the <code>DISCUSS</code> announcing the vote has been cancelled and explain why and that you’re going to start a new RC soon. Ideally prefix the title of the Emails with <code>[CANCELLED]</code></p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>After this you should be ready to start a new RC.</p>
+</div>
+</div>
+<div class="sect2">
<h3 id="cleaning_up_older_release_versions">Cleaning up older release versions</h3>
<div class="paragraph">
<p>As a lot of mirrors are serving our releases, it is the Apache policy to clean old releases from the repo if newer versions are released.</p>
