Apache Unomi Release Guide

The Apache Unomi project periodically declares and publishes releases. A release is one or more packages of the project artifact(s) that are approved for general public distribution and use. They may come with various degrees of caveat regarding their perceived quality and potential for change, such as "alpha", "beta", "stable", etc.

The Unomi community treats releases with great importance. They are a public face of the project and most users interact with the project only through the releases. Releases are signed off by the entire Unomi community in a public vote.

Each release is executed by a Release Manager, who is selected among the Unomi committers. This document describes the process that the Release Manager follows to perform a release. Any changes to this process should be discussed and adopted on the dev@ mailing list.

Please remember that publishing software has legal consequences. This guide complements the foundation-wide Product Release Policy and Release Distribution Policy.


Apache Unomi release guide

The release process consists of several steps:

  1. Decide to release
  2. Prepare for the release
  3. Build a release candidate
  4. Vote on the release candidate
  5. During vote process, run validation tests
  6. If necessary, fix any issues and go back to step 3.
  7. Finalize the release
  8. Promote the release

Decide to release

Deciding to release and selecting a Release Manager is the first step of the release process. This is a consensus-based decision of the entire community.

Anybody can propose a release on the dev@ mailing list, giving a solid argument and nominating a committer as the Release Manager (including themselves). There's no formal process, no vote requirements, and no timing requirements. Any objections should be resolved by consensus before starting the release.

In general, the community prefers to have a rotating set of 3-5 Release Managers. Keeping a small core set of managers allows enough people to build expertise in this area and improve processes over time, without Release Managers needing to re-learn the processes for each release. That said, if you are a committer interested in serving the community in this way, please reach out to the community on the dev@ mailing list.

Basically we will be following the procedure described here with a few more steps and details before and after.

Checklist to proceed to the next step

  1. Community agrees to release
  2. Community selects a Release Manager

Prepare for the release


  1. Setup new version in JIRA project
  2. Update all JIRAs, close the ones that are still not closed, review tickets that can be closed, postpone to another release tickets that are not managed now


  1. Clone and checkout the project using:
    git clone https://gitbox.apache.org/repos/asf/unomi.git
    in a separate directory, to make sure you don’t have any additional files in the build (such as allCountries.zip or other binary files that should not be there)

Build the project

  1. Tests source, javadocs and signature generation using:
    mvn clean install -P apache-release,integration-tests
  2. Make sure we generate all sub-projects using:
    mvn clean install -DskipTests=true
    -P integration-tests,performance-tests,rat,apache-release
  3. 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 :
    less target/unomi-root-1.4.0-SNAPSHOT.rat
  4. 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)
  5. Update the copyright notice years in the NOTICE file and anywhere else where it might be
  6. If you get JavaDoc errors or other errors you must correct all of them before proceeding further
  7. If you get a error while signing despite having the proper keys install that looks like this:
    [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
    you can either try to sign a file like this:
    gpg -ab test.txt
    this will ask for your password and remember it in the agent for a while, or if you want a more permanent solution: https://dan.cx/2016/11/gpg-inappropriate-ioctl-for-device-errors

Publish the release


  1. Setup server passwords for publishing as document here: https://www.apache.org/dev/publishing-maven-artifacts.html and https://maven.apache.org/guides/mini/guide-encryption.html#How_to_encrypt_server_passwords
  2. Check into the target directory and unzip the source release and compile it using:
    cd target
    unzip unomi-root-1.4.0-SNAPSHOT-source-release.zip
    cd unomi-root-1.4.0-SNAPSHOT
    mvn clean install
    to check that the packaged source build properly
  3. Go back to the root project directory and run:
    mvn release:prepare -DskipTests=true -DdryRun=true
    -P apache-release,integration-tests,performance-tests
  4. Publish a snapshot to test the deployment passwords:
    mvn deploy
  5. Delete the release.properties file
    rm release.properties
  6. mvn -P apache-release,integration-tests release:prepare
  7. mvn -DskipITs=true -DskipTests=true -P integration-tests release:perform
  8. If something fails, make sure you first drop the staging repository created here: https://repository.apache.org/#stagingRepositories.
    If you need to relaunch the release:perform and don’t have a release.properties, create a release.properties file with the following contents:
    and run mvn release:perform
  9. Make sure you uploaded your public PGP key using:
    gpg --keyserver hkp://pgp.mit.edu --send-keys KEY_IDENTIFIER
    (get the identifier using gpg --list-secret-keys).
    This will be used by the Apache Nexus Repository Manager to validate the JARs uploaded in the staging repository.
  10. Connect to https://repository.apache .org/#stagingRepositories and look for the open staging repositories, you should have two (one for everything and the other for KAR/features) for releases <= 1.2 and just one for versions >= 1.3.0 (because of changes in the Karaf plugins). Close the repositories and given a meaningful comment when closing such as:
    Apache Unomi 1.4.0 Release


  1. Send out to the Unomi mailing list a mail to start the voting process, see [1]
  2. Send out a vote summary in the same thread to the Unomi mailing list once the voting period has expired, see [2]
  3. Upload the source and binary distributions to the Apache Dist repository before the PMC vote:
    svn checkout https://dist.apache.org/repos/dist/dev/unomi unomi-dev
  4. cd unomi-dev
    mkdir 1.4.0
  5. Copy all the Zip and Tarbars including SHA1/ASC (but do not copy the MD5 sum) files from: https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi/1.4.0/ and https://repository.apache.org/content/repositories/orgapacheunomi-1014/org/apache/unomi/unomi-root/1.4.0/
  6. Rename the source files to something shorter and consistent with previous releases:
    mv unomi-root-1.4.0-source-release.zip unomi-1.4.0-src.zip
    mv unomi-root-1.4.0-source-release.zip.asc unomi-1.4.0-src.zip.asc
    mv unomi-root-1.4.0-source-release.zip.md5 unomi-1.4.0-src.zip.md5
    mv unomi-root-1.4.0-source-release.zip.sha1 unomi-1.4.0-src.zip.sha1
  7. cd ..
    svn add 1.4.0
  8. If needed, update the KEYS file (that is in the svn checkout https://dist.apache.org/repos/dist/release/unomi)
  9. svn commit -m "Apache 1.4.0 Release (for PMC voting)"
  10. 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:
    mvn versions:set
  11. Promote the staging repositories now that the release is approved

Finalize the release

  1. Move the files uploaded to the unomi-dev repository to the unomi-release repository by doing the following:
    svn mv https://dist.apache.org/repos/dist/dev/unomi/1.4.0
    -m "Apache Unomi 1.4.0 Release"
  2. Update Jenkins
  3. In JIRA mark the version as released and add a release date
  4. Connect to https://repository.apache.org/#stagingRepositories and look for the open staging repositories, you should have one. Select the staging repositoriy and click on release.
  5. Update the website to point to the new release on the download page by first copying the current release to the archive page. Make sure you change the links to use the archive.apache.org instead of the closer.lua script (see other archived versions for example). Then you can update the download page with the proper links to the new release (no direct links to www.apache.org/dist, make sure you use the closer.lua script). Be careful with links that contain & (ampersand) characters, they must be replaced with & Finally on the home page update the news section to add the release.


  1. Check the generated site by opening target/staging/index.html and check your changes and verify that there are no broken links
  2. WAIT FOR THE MIRRORS TO SYNC (at least 24 hours)
  3. Upload the site modification by using:
    ./generate-site-and-upload.sh APACHE_LDAP_USERNAME APACHE_LDAP_PASSWORD


  1. Delete the tag:
    git push --delete origin unomi-root-1.4.0
    git tag --delete unomi-root-1.4.0
  2. Reset to the previous commit before the release preparation:
    git reset --hard c65f9897ec5f31d9d22ad639738c7db9d109aa77
    git push origin -f


  1. Send an announce to the project mailing list and the incubator mailing list to announce the new release using mail template [3]
  2. If you were releasing from a branch, make sure you merge all the branch changes for the release back to the master.

Social media

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

Checklist to declare the process completed

  1. Release announced on the user@ mailing list.
  2. Release recorded in reporter.apache.org.
  3. Release announced on social media.
  4. Completion declared on the dev@ mailing list.

Improve the process

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.

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!

Mail templates

[1] Mail template for the Unomi PMC vote:

Subject: [VOTE] Apache Unomi 1.4.0 release [TAKE2]
Hi all,

I submit Apache Unomi 1.4.0 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:

You can find the sources here :


Convenience binaries are also available here:

Git tag:

Release Notes:

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.

[2] Mail template for the results of the Unomi PMC vote:

Subject: [RESULT][VOTE] Apache Unomi 1.4.0 release [TAKE2]

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 1.4.0 is approved by the team.

John Doe 1
[3] Announce mailing list template:

Subject : [ANNOUNCE] Apache Unomi 1.4.0 Release
The Apache Unomi team would like to announce the release of Apache
Unomi 1.4.0.

Release notes are here:

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’

More details regarding Apache Unomi can be found here:

The release artifacts can be downloaded here:

All JIRAs completed for this release are tagged with 'FixVersion =
1.4.0'; the JIRA release notes can be found here:

The Apache Unomi Team