src/main/webapp/contribute/manual-release-guide.html [397:581]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                <li>
                    Go back to the site project and make sure you update the documentation page to link to the proper
                    versions of the documents.
                </li>
            </ol>

            <h3 id="final-docker">Docker image</h3>

            <ol>
                <li>
                    Checkout the tagged version:
                    <pre class="alert alert-primary"><code>git checkout tags/unomi-root-${next.stable.version}</code></pre>
                </li>
                <li>
                    Change to the Docker directory. Make sure you have docker running locally (start Docker Desktop for
                    example):
                    <pre class="alert alert-primary"><code>cd docker</code></pre>
                </li>
                <li>
                    Launch the docker build and push
                    <pre class="alert alert-primary"><code>mvn clean install
mvn docker:push</code></pre>
                </li>
            </ol>


            <h3 id="rollback">Rollback</h3>
            <ol>
              <li>Delete the tag:
                <pre class="alert alert-primary"><code>git push --delete origin unomi-root-${next.stable.version}
git tag --delete unomi-root-${next.stable.version}</code></pre>
              </li>
              <li>Reset to the previous commit before the release preparation:
                <pre class="alert alert-primary"><code>git reset --hard c65f9897ec5f31d9d22ad639738c7db9d109aa77
git push origin -f</code></pre>
              </li>
            </ol>

            <h2 id="final">Announce</h2>

            <ol>
              <li>Send an announce to the project mailing list and the Apache announce mailing list to announce the new release using mail template <a href="#mail-3">[3]</a></li>
              <li>If you were releasing from a branch, make sure you merge all the branch changes for the release back to the master.</li>
            </ol>

            <h3 id="social-media">Social media</h3>

            <p>Tweet, post on Facebook, LinkedIn, and other platforms. Ask other contributors to do the same.</p>

              <h3 id="remove-old-releases">Remove old releases</h3>

              <p>
                  In order to lighten the load on mirrors, remove old releases from the dist server once the new release
                  has properly been deployed to all the mirrors. Old releases are automatically archived so they are
                  not needed on the mirrors anymore. Just make sure that all the links in the download page do point
                  to the archive server.
              </p>

            <h3 id="checklist-to-declare-the-process-completed">Checklist to declare the process completed</h3>

            <ol>
              <li>Release announced on the user@ mailing list.</li>
              <li>Release recorded in reporter.apache.org.</li>
              <li>Release announced on social media.</li>
              <li>Completion declared on the dev@ mailing list.</li>
                <li>Check that old release where removed from the dist server</li>
            </ol>

            <h2 id="improve-the-process">Improve the process</h2>

            <p>It is important that we improve the release processes over time. Once you’ve finished the release, please take a step back and look what areas of this process and be improved. Perhaps some part of the process can be simplified. Perhaps parts of this guide can be clarified.</p>

            <p>If we have specific ideas, please start a discussion on the dev@ mailing list and/or propose a pull request to update this guide. Thanks!</p>

            <hr />

            <h2 id="mail-template">Mail templates</h2>

            <h6 id="mail-1" class="pt-3">[1] Mail template for the Unomi PMC vote:</h6>
            <pre class="alert alert-primary"><code>
Subject: [VOTE] Apache Unomi ${next.stable.version} release [TAKE2]
Body:
Hi all,

I submit Apache Unomi ${next.stable.version} release [TAKE2] to your vote.

The following corrections were done since TAKE 1:
NOTICE year (2016) has been updated to 2018
unexpected binaries inside zip file [1] : zip file has been completely removed
All artefacts are now signed in an apache email address

Staging Repository:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/
&lt;https://repository.apache.org/content/repositories/orgapacheunomi-1021/&gt;*

You can find the sources here :

*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip
&lt;https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip&gt;*

Convenience binaries are also available here:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
unomi/unomi/${next.stable.version}/
&lt;https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
unomi/unomi/${next.stable.version}/&gt;*

Git tag:
unomi-root-${next.stable.version}

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&
version=12341610

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours, or until the necessary number
of binding votes (3 +1) is reached.

Please let me know if you have any questions.

Thanks,
Regards
            </code></pre>

            <h6 id="mail-2" class="pt-3">[2] Mail template for the results of the Unomi PMC vote:</h6>
            <pre class="alert alert-primary"><code>
Subject: [RESULT][VOTE] Apache Unomi ${next.stable.version} release [TAKE2]
Body:
Hi,

Thank you for your votes.

Here's the summary :

3 binding votes +1:

John Doe 1
John Doe 2
John Doe 3

2 non-binding vote +1:
John Doe 4
John Doe 5

No 0 or -1.

The proposal to release Unomi ${next.stable.version} is approved by the team.

Thanks,
John Doe 1
            </code></pre>

            <h6 id="mail-3" class="pt-3">[3] Announce mailing list template:</h6>
            <pre class="alert alert-primary"><code>
Subject : [ANNOUNCE] Apache Unomi ${next.stable.version} Release
Body:
The Apache Unomi team would like to announce the release of Apache
Unomi ${next.stable.version}.

Release notes are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&
version=12338361

Apache Unomi is a Java Open Source customer data platform, a Java server
designed to manage customers, leads and visitors' data and help personalize customers'
experiences.

More details regarding Apache Unomi can be found here:
http://unomi.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/unomi/${next.stable.version}/

All JIRAs completed for this release are tagged with 'FixVersion =
${next.stable.version}'; the JIRA release notes can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&
version=12338361

Thanks!
The Apache Unomi Team
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -



src/main/webapp/contribute/release-guide.html [290:474]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                <li>
                    Go back to the site project and make sure you update the documentation page to link to the proper
                    versions of the documents.
                </li>
            </ol>

            <h3 id="final-docker">Docker image</h3>

            <ol>
                <li>
                    Checkout the tagged version:
                    <pre class="alert alert-primary"><code>git checkout tags/unomi-root-${next.stable.version}</code></pre>
                </li>
                <li>
                    Change to the Docker directory. Make sure you have docker running locally (start Docker Desktop for
                    example):
                    <pre class="alert alert-primary"><code>cd docker</code></pre>
                </li>
                <li>
                    Launch the docker build and push
                    <pre class="alert alert-primary"><code>mvn clean install
mvn docker:push</code></pre>
                </li>
            </ol>


            <h3 id="rollback">Rollback</h3>
            <ol>
              <li>Delete the tag:
                <pre class="alert alert-primary"><code>git push --delete origin unomi-root-${next.stable.version}
git tag --delete unomi-root-${next.stable.version}</code></pre>
              </li>
              <li>Reset to the previous commit before the release preparation:
                <pre class="alert alert-primary"><code>git reset --hard c65f9897ec5f31d9d22ad639738c7db9d109aa77
git push origin -f</code></pre>
              </li>
            </ol>

            <h2 id="final">Announce</h2>

            <ol>
              <li>Send an announce to the project mailing list and the Apache announce mailing list to announce the new release using mail template <a href="#mail-3">[3]</a></li>
              <li>If you were releasing from a branch, make sure you merge all the branch changes for the release back to the master.</li>
            </ol>

            <h3 id="social-media">Social media</h3>

            <p>Tweet, post on Facebook, LinkedIn, and other platforms. Ask other contributors to do the same.</p>

              <h3 id="remove-old-releases">Remove old releases</h3>

              <p>
                  In order to lighten the load on mirrors, remove old releases from the dist server once the new release
                  has properly been deployed to all the mirrors. Old releases are automatically archived so they are
                  not needed on the mirrors anymore. Just make sure that all the links in the download page do point
                  to the archive server.
              </p>

            <h3 id="checklist-to-declare-the-process-completed">Checklist to declare the process completed</h3>

            <ol>
              <li>Release announced on the user@ mailing list.</li>
              <li>Release recorded in reporter.apache.org.</li>
              <li>Release announced on social media.</li>
              <li>Completion declared on the dev@ mailing list.</li>
                <li>Check that old release where removed from the dist server</li>
            </ol>

            <h2 id="improve-the-process">Improve the process</h2>

            <p>It is important that we improve the release processes over time. Once you’ve finished the release, please take a step back and look what areas of this process and be improved. Perhaps some part of the process can be simplified. Perhaps parts of this guide can be clarified.</p>

            <p>If we have specific ideas, please start a discussion on the dev@ mailing list and/or propose a pull request to update this guide. Thanks!</p>

            <hr />

            <h2 id="mail-template">Mail templates</h2>

            <h6 id="mail-1" class="pt-3">[1] Mail template for the Unomi PMC vote:</h6>
            <pre class="alert alert-primary"><code>
Subject: [VOTE] Apache Unomi ${next.stable.version} release [TAKE2]
Body:
Hi all,

I submit Apache Unomi ${next.stable.version} release [TAKE2] to your vote.

The following corrections were done since TAKE 1:
NOTICE year (2016) has been updated to 2018
unexpected binaries inside zip file [1] : zip file has been completely removed
All artefacts are now signed in an apache email address

Staging Repository:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/
&lt;https://repository.apache.org/content/repositories/orgapacheunomi-1021/&gt;*

You can find the sources here :

*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip
&lt;https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
unomi/unomi-root/${next.stable.version}/unomi-root-${next.stable.version}-source-release.zip&gt;*

Convenience binaries are also available here:
*https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
unomi/unomi/${next.stable.version}/
&lt;https://repository.apache.org/content/repositories/orgapacheunomi-1021/org/apache/
unomi/unomi/${next.stable.version}/&gt;*

Git tag:
unomi-root-${next.stable.version}

Release Notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&
version=12341610

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours, or until the necessary number
of binding votes (3 +1) is reached.

Please let me know if you have any questions.

Thanks,
Regards
            </code></pre>

            <h6 id="mail-2" class="pt-3">[2] Mail template for the results of the Unomi PMC vote:</h6>
            <pre class="alert alert-primary"><code>
Subject: [RESULT][VOTE] Apache Unomi ${next.stable.version} release [TAKE2]
Body:
Hi,

Thank you for your votes.

Here's the summary :

3 binding votes +1:

John Doe 1
John Doe 2
John Doe 3

2 non-binding vote +1:
John Doe 4
John Doe 5

No 0 or -1.

The proposal to release Unomi ${next.stable.version} is approved by the team.

Thanks,
John Doe 1
            </code></pre>

            <h6 id="mail-3" class="pt-3">[3] Announce mailing list template:</h6>
            <pre class="alert alert-primary"><code>
Subject : [ANNOUNCE] Apache Unomi ${next.stable.version} Release
Body:
The Apache Unomi team would like to announce the release of Apache
Unomi ${next.stable.version}.

Release notes are here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&
version=12338361

Apache Unomi is a Java Open Source customer data platform, a Java server
designed to manage customers, leads and visitors' data and help personalize customers'
experiences.

More details regarding Apache Unomi can be found here:
http://unomi.apache.org/

The release artifacts can be downloaded here:
https://dist.apache.org/repos/dist/release/incubator/unomi/${next.stable.version}/

All JIRAs completed for this release are tagged with 'FixVersion =
${next.stable.version}'; the JIRA release notes can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319220&
version=12338361

Thanks!
The Apache Unomi Team
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -