Releasing

New releasing using technical account:

1. check that everything you want to release is pushed in the master branch: https://github.com/gooddata/gooddata-java/commits/master

2. decide right version (use semantic versioning scheme)

3. use java-libraries/gooddata-java-release Jenkins job

   • Use full LIBRARY_VERSION including API version (from gooddata-java-model/src/main/resources/GoodDataApiVersion), e.g. 3.8.0+api3

   (In case there are some problems uploading to Sonatype, check status page. If staging repository operations are timing out from cmdline, one can kill mvn task after it uploads artefacts to staging repo and then close and/or release it in the web UI.)

4. close (and rename if necessary) current milestone (and create new one named "next")

5. create a new release

6. wait for Maven Central sync

---

Old, manual releasing using personal accounts:

1. decide right version (use semantic versioning scheme)

2. check your current fork and branch to be gooddata/gooddata-java:master

3. run the release using ./release.sh -v <decided version> (you'll be asked for your GPG password or you can add -g <gpg password> parameter)

   (API version is appended automatically from gooddata-java-model/src/main/resources/GoodDataApiVersion.)

   (JDK 11 is required for build.)

   (In case there are some problems uploading to Sonatype, check status page. If staging repository operations are timing out from cmdline, one can kill mvn task after it uploads artefacts to staging repo and then close and/or release it in the web UI.)

4. close (and rename if necessary) current milestone (and create new one named "next")

5. create a new release

6. wait for Maven Central sync

---

In case the release script (release.sh) somehow fails, or you don't like the auto-magic, you can replace that step with:

• change version in README.md and commit "bump version"
• release using Maven release plugin mvn release:prepare release:perform
• git push origin --tags HEAD