src/main/webapp/contribute/manual-release-guide.html [289:361]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                <li>Send out to the Unomi mailing list a mail to start the voting process, see <a href="#mail-1">[1]</a></li>
                <li>If the vote is refused or cancelled, peform the following steps to restart the release process:
                    <ol>
                        <li>Drop the release in <a href="https://repository.apache.org/#stagingRepositories" target="_blank">Nexus</a></li>
                        <li>Remove the tag in Git:
                            <pre class="alert alert-primary"><code>git push --delete origin unomi-root-${next.stable.version}
git tag -d unomi-root-${next.stable.version}</code></pre>
                        </li>
                        <li>Correct any problems in the source, make sure to do them in master and cherry-pick them to the relevant branches</li>
                        <li>Reset all versions with the following command:
                            <pre class="alert alert-primary"><code>mvn versions:set -DskipITs=true -DskipTests=true -P integration-tests,rat,apache-release,docker,\!run-tests</code></pre>
                        </li>
                        <li>Restart at the release:prepare step</li>
                    </ol>
                </li>
              <li>
                If the vote is refused, you will need to restart the release process. Make sure you remove the staging repositories as well as the release tag. You will also need to reset the version in the project using:
                <pre class="alert alert-primary"><code>mvn versions:set</code></pre>
              </li>
                <li>Send out a vote summary in the same thread to the Unomi mailing list once the voting period has expired, see <a href="#mail-2">[2]</a></li>
            </ol>

            <h2 id="finalize-release">Finalize the release</h2>
            <ol>
              <li>
                Move the files uploaded to the unomi-dev repository to the unomi-release repository by doing the following:
                <pre class="alert alert-primary"><code>svn mv https://dist.apache.org/repos/dist/dev/unomi/${next.stable.version} https://dist.apache.org/repos/dist/release/unomi/${next.stable.version} -m "Apache Unomi ${next.stable.version} Release"</code></pre>
              </li>
              <li>
                In JIRA mark the version as released and add a release date
              </li>
              <li>
                Connect to <a href="https://repository.apache.org/#stagingRepositories" target="_blank">https://repository.apache.org/#stagingRepositories</a> and look for the open staging repositories, you should have one. Select the staging repositoriy and click on <code>release</code>.
              </li>
              <li>Update the website (in project `unomi-site`) to point to the new release on the download page by
                  first copying the previous archive release and replacing all the version numbers with the current release
                  version. Also don't forget to copy the release notes. Then you can update the download page with the proper
                  links to the new release (no direct links to <code>www.apache.org/dist</code>, make sure you use the closer.lua script).
                  Be careful with links that contain & (ampersand) characters, they must be replaced with &amp;. Normally all
                  this should be easy to do by simply search & replacing the version number. Finally on the home page update the news section to add the release.
                  <pre class="alert alert-primary"><code>git clone https://gitbox.apache.org/repos/asf/unomi-site.git</code></pre>
                  Perform any modifications, notably change the versions in the pom.xml file:
                  <pre class="alert alert-primary"><code>    &lt;properties&gt;
        &lt;latest.stable.version&gt;1.5.4&lt;/latest.stable.version&gt;
        &lt;next.development.version&gt;1.5.5-SNAPSHOT&lt;/next.development.version&gt;
        &lt;next.stable.version&gt;1.5.5&lt;/next.stable.version&gt;
        &lt;latest.development.version&gt;2.0.0-SNAPSHOT&lt;/latest.development.version&gt;
    &lt;/properties&gt;
</code></pre>
                 Then modify the index.html, download.html to add the new files. For the documentation see the next step.
              </li>
                <li>
                  Test the site modifications using the generated site HTML using Jekyll serve
                    <pre class="alert alert-primary"><code>./mvnw clean install gem:exec@jekyll-serve-filtered</code></pre>
                    Connect to http://127.0.0.1:4000 to check the modifications. If you need to make more modifications,
                    simply relaunch the above line after modifying the HTML files.
                </li>
                <li>
                  Deploy the web site changes using:
                  <pre class="alert alert-primary"><code>./mvnw clean install
./mvnw install scm-publish:publish-scm -Dusername=YOUR_APACHE_USERNAME -Dpassword=YOUR_APACHE_PASSWORD</code></pre>
                </li>
                <li>
                  Then make sure to commit all the changes to the web site's git project:
                  <pre class="alert alert-primary"><code>git commit -m "Apache Unomi ${next.stable.version} Release website update"
git push</code></pre>
              </li>
            </ol>

            <h3 id="final-documentation">Documentation</h3>

            <ol>
                <li>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



src/main/webapp/contribute/release-guide.html [207:279]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                <li>Send out to the Unomi mailing list a mail to start the voting process, see <a href="#mail-1">[1]</a></li>
                <li>If the vote is refused or cancelled, peform the following steps to restart the release process:
                    <ol>
                        <li>Drop the release in <a href="https://repository.apache.org/#stagingRepositories" target="_blank">Nexus</a></li>
                        <li>Remove the tag in Git:
                            <pre class="alert alert-primary"><code>git push --delete origin unomi-root-${next.stable.version}
git tag -d unomi-root-${next.stable.version}</code></pre>
                        </li>
                        <li>Correct any problems in the source, make sure to do them in master and cherry-pick them to the relevant branches</li>
                        <li>Reset all versions with the following command:
                            <pre class="alert alert-primary"><code>mvn versions:set -DskipITs=true -DskipTests=true -P integration-tests,rat,apache-release,docker,\!run-tests</code></pre>
                        </li>
                        <li>Restart at the release:prepare step</li>
                    </ol>
                </li>
              <li>
                If the vote is refused, you will need to restart the release process. Make sure you remove the staging repositories as well as the release tag. You will also need to reset the version in the project using:
                <pre class="alert alert-primary"><code>mvn versions:set</code></pre>
              </li>
                <li>Send out a vote summary in the same thread to the Unomi mailing list once the voting period has expired, see <a href="#mail-2">[2]</a></li>
            </ol>

            <h2 id="finalize-release">Finalize the release</h2>
            <ol>
              <li>
                Move the files uploaded to the unomi-dev repository to the unomi-release repository by doing the following:
                <pre class="alert alert-primary"><code>svn mv https://dist.apache.org/repos/dist/dev/unomi/${next.stable.version} https://dist.apache.org/repos/dist/release/unomi/${next.stable.version} -m "Apache Unomi ${next.stable.version} Release"</code></pre>
              </li>
              <li>
                In JIRA mark the version as released and add a release date
              </li>
              <li>
                Connect to <a href="https://repository.apache.org/#stagingRepositories" target="_blank">https://repository.apache.org/#stagingRepositories</a> and look for the open staging repositories, you should have one. Select the staging repositoriy and click on <code>release</code>.
              </li>
              <li>Update the website (in project `unomi-site`) to point to the new release on the download page by
                  first copying the previous archive release and replacing all the version numbers with the current release
                  version. Also don't forget to copy the release notes. Then you can update the download page with the proper
                  links to the new release (no direct links to <code>www.apache.org/dist</code>, make sure you use the closer.lua script).
                  Be careful with links that contain & (ampersand) characters, they must be replaced with &amp;. Normally all
                  this should be easy to do by simply search & replacing the version number. Finally on the home page update the news section to add the release.
                  <pre class="alert alert-primary"><code>git clone https://gitbox.apache.org/repos/asf/unomi-site.git</code></pre>
                  Perform any modifications, notably change the versions in the pom.xml file:
                  <pre class="alert alert-primary"><code>    &lt;properties&gt;
        &lt;latest.stable.version&gt;1.5.4&lt;/latest.stable.version&gt;
        &lt;next.development.version&gt;1.5.5-SNAPSHOT&lt;/next.development.version&gt;
        &lt;next.stable.version&gt;1.5.5&lt;/next.stable.version&gt;
        &lt;latest.development.version&gt;2.0.0-SNAPSHOT&lt;/latest.development.version&gt;
    &lt;/properties&gt;
</code></pre>
                 Then modify the index.html, download.html to add the new files. For the documentation see the next step.
              </li>
                <li>
                  Test the site modifications using the generated site HTML using Jekyll serve
                    <pre class="alert alert-primary"><code>./mvnw clean install gem:exec@jekyll-serve-filtered</code></pre>
                    Connect to http://127.0.0.1:4000 to check the modifications. If you need to make more modifications,
                    simply relaunch the above line after modifying the HTML files.
                </li>
                <li>
                  Deploy the web site changes using:
                  <pre class="alert alert-primary"><code>./mvnw clean install
./mvnw install scm-publish:publish-scm -Dusername=YOUR_APACHE_USERNAME -Dpassword=YOUR_APACHE_PASSWORD</code></pre>
                </li>
                <li>
                  Then make sure to commit all the changes to the web site's git project:
                  <pre class="alert alert-primary"><code>git commit -m "Apache Unomi ${next.stable.version} Release website update"
git push</code></pre>
              </li>
            </ol>

            <h3 id="final-documentation">Documentation</h3>

            <ol>
                <li>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -