The scenarioo-java
repository has two branches: develop
for developing the next release and master
for all published releases.
Precondition: Before considering a release, make sure that the new version is well tested. If you are not 100% sure about the quality of the code, make a release candidate first and test it well in a realistic environment.
- Finalize the code in the
develop
branch ofscenarioo-java
by setting the correct version number in thebuild.gradle
file. This version number must not exist yet in mavem central. RemoveSNAPSHOT
from the version number and add-RCx
for release candidates wherex
is the RC number for further release candidate testing. - You have to manually Publish the signed snapshot to maven central) this is currently not automated.
- Make sure the changelog.md is updated for the new version
- Precondition: see Prepare Release above.
- Set the final version number in develop or release branch (without
-SNAPSHOT
or-RC
) inbuild.gradle
and merge it to the develop branch (or the release branch). - You have to manually Publish the signed release to maven central) this is currently not automated.
- Promote the final release to maven central: http://central.sonatype.org/pages/releasing-the-deployment.html
- Add a tag with the release version number to the commit where you set that version number and push the tag.
- Write Release Notes for the new release on GitHub (here)
- Merge the release branch to master.
- IMPORTANT - Increase Version to next snapshot version on Develop Branch: Checkout
develop
again, change the version inbuild.gradle
to the nextx.y.z-SNAPSHOT
version and commit.x.y
corresponds to the last release version andz
is incremented by one compared to the last release. - Switch Scenarioo Viewer Webapp to newest version: Go to repo
scenarioo
and change the version of the writer library used to the newest version and commit and push (--> PR to next release branch or to develop).