13. SCD4J Developers

Steps to Release

1. Run unit tests

• Pay attention because some tests requires root access to run (3, actually)

3. Run a manual test (just in case)

• Use uploadArchive gradle task for dev publishing
• Use gradle-examples for your manual tests
  • Pay attention because some examples requires root access to run

4. Execute bintrayUpload gradle task

• If everything gonna ok, BINTRAY_DEPLOY_NUMBER will be incremented in version.properties
  • The new number is supposed to represent the next Bintray deployment
• The generated version will be deployed in Bintray
• IMPORTANT: this step requires gradle.properties file with bintray_user and bintray_api_key properties

5. Wait the new version be published in gradle plugins web site

• Relax and drink a coffee, it gonna take a while (I mean, it may take hours)

6. Run sudo ./update_scd4j_version.sh 'VERSION_NUMBER' in scd4j-examples dir

• This is required to update scd4j version in all example projects and to make sure the examples will be 100% ready to go

7. If everything is ok, refresh the workspace, pull, commit and push everithing to GitHub
8. Tag the project

• The tag name must be the exact version number shown in the logs during bintrayUpload.
• The tag description should be a very short description

9. Go to GitHub and create a new release from the just created tag

• Enter the release notes in description