Release Process

TODO: the release process is too manual and needs to be automated

The release process consists of these steps:

Edit build.gradle and remove the -SNAPSHOT suffix from the version parameter
Add an entry to CHANGELOG.pm with description of changes in the new release
Commit as "Preparing release"
Run make release
Once the artifacts are uploaded to Sonatype staging, release them to Maven Central

https://oss.sonatype.org/, log in, go to Staging Repositories
In the top-right corner search box type uber, and find your uploaded repository
Hit Close button. Monitor status on Activity tab at the bottom, hitting Refresh.
Once Close is successful, the Release button will become available, so hit it
Keep hitting Refresh while sync to Maven is in progress. Once it's complete, the repository will disappear.

Bump the version in build.gradle to the next release and add `-SNAPSHOT suffix
Commit as "Back to development"

The uploadArchives step performs signing of the artifacts. For that to work the script requires private/public keys.

install GPG: brew install gpg
generate keys: gpg --gen-key
see installed keys with gpg --list-keys or gpg --list-secret-keys
create an account with Sonatype, get repo permissions (e.g. https://issues.sonatype.org/browse/OSSRH-23572)
create $HOME/.gradle/gradle.properties file

    signing.keyId={key ID from gpg --list-secret-keys}
    signing.password={password you used to encrypt keys via gpg --gen-key}
    signing.secretKeyRingFile={e.g. [home path]/.gnupg/secring.gpg}

    ossrhUsername={your user name at Sonatype}
    ossrhPassword={your password at Sonatype}

upload your public key to Ubuntu servers, e.g.
- gpg --keyserver http://keyserver.ubuntu.com:11371 --send-keys {pub key ID}
- you can also use Web UI and upload plain test key that you can obtain via
  - gpg --armor --export {your email used for the keys}