src/main/webapp/contribute/manual-release-guide.html [179:200]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
              <li>Check that there are no JARs or ZIP files in the source code, you can do this by looking at the generated RAT report here :
                <pre class="alert alert-primary"><code>less target/unomi-root-${next.development.version}.rat</code></pre>
              </li>
              <li>Check that the KEYS file only contains signatures with @apache.org addresses (if there are non @apache.org don’t remove them because they have
                been used to sign older releases)
              </li>
              <li>Check the Copyright notice years in the NOTICE file and anywhere else where it might be (by using search and replace)</li>
              <li>If you get JavaDoc errors or other errors you must correct all of them before proceeding further</li>
              <li>If you get a error while signing despite having the proper keys install that looks like this:
                <pre class="alert alert-primary"><code>[INFO] --- maven-gpg-plugin:1.5:sign (default) @ unomi-root ---
gpg: 'echec de la signature : Inappropriate ioctl for device
gpg: signing failed: Inappropriate ioctl for device</code></pre>
                you can either try to sign a file like this:
                <pre class="alert alert-primary"><code>gpg -ab test.txt</code></pre>
                this will ask for your password and remember it in the agent for a while, or if you want a more permanent solution: <a href="https://dan.cx/2016/11/gpg-inappropriate-ioctl-for-device-errors" target="_blank">https://dan.cx/2016/11/gpg-inappropriate-ioctl-for-device-errors</a>
              </li>
            </ol>

            <h2 id="publish-the-release">Publish the release</h2>
            <h3 id="publish-repository">Repository</h3>

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



src/main/webapp/contribute/release-guide.html [168:188]:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
              <li>Check that there are no JARs or ZIP files in the source code, you can do this by looking at the generated RAT report here :
                <pre class="alert alert-primary"><code>less target/unomi-root-${next.development.version}.rat</code></pre>
              </li>
              <li>Check that the KEYS file only contains signatures with @apache.org addresses (if there are non @apache.org don’t remove them because they have
                been used to sign older releases)
              </li>
              <li>Check the Copyright notice years in the NOTICE file and anywhere else where it might be (by using search and replace)</li>
              <li>If you get JavaDoc errors or other errors you must correct all of them before proceeding further</li>
              <li>If you get a error while signing despite having the proper keys install that looks like this:
                <pre class="alert alert-primary"><code>[INFO] --- maven-gpg-plugin:1.5:sign (default) @ unomi-root ---
gpg: 'echec de la signature : Inappropriate ioctl for device
gpg: signing failed: Inappropriate ioctl for device</code></pre>
                you can either try to sign a file like this:
                <pre class="alert alert-primary"><code>gpg -ab test.txt</code></pre>
                this will ask for your password and remember it in the agent for a while, or if you want a more permanent solution: <a href="https://dan.cx/2016/11/gpg-inappropriate-ioctl-for-device-errors" target="_blank">https://dan.cx/2016/11/gpg-inappropriate-ioctl-for-device-errors</a>
              </li>
            </ol>

            <h2 id="publish-the-release">Publish the release</h2>
            <h3 id="publish-repository">Repository</h3>
              <ol>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -