RELEASES.adoc

How To Release

This document contains some information about the CI build and deployment. Other infos are present in the top README.

CI Build

Table 1. Build Server

server	master	develop	configuration
Travis-CI.com			s. .travis.yml
Travis-CI.org (old)			s. .travis.yml
sonarcloud.io			sonar:sonar

The CI build is started automatically after a commit and push to GitHub.

Release Notes

see CHANGELOG.

Deployment

This is a little checklist for the next release:

Ordered

1. create a release branch and change to it

2. remove -SNAPSHOT in pom.xml

3. build all artifacts: mvn -B clean install source:jar javadoc:jar gpg:sign -Dgpg.passphrase=xx

4. use the script src/script/deploy.sh to upload bundles to https://oss.sonatype.org/ (but don’t forget to update the VERSION variable inside this script).

5. after upload to the staging repository release it: select Staging Repositories on oss.sonatype.org, press "Refresh" and then "Close" and "Release".

6. build the Javadoc (mvn javadoc:javadoc) and transfer target/apidoc to http://javatux.de/j4cups/

7. checkin the pom.xml (if not already done), label the sources, e.g. with "j4cups-0.6.0" and push it (git push --tags)

8. merge the release branch to master and develop branch

9. change to develop branch and start next SNAPSHOT

10. after a few days: check j4cups with search.maven.org