Development Process

The development/release process has changed and now works with Github packages. To use the latest release, follow instructions as per the README on the project repository.

Preparing for new development

New development should be created as a branch out of develop branch. Use prefix feature/ and a suitable name, eg. feature/selenium10.

develop branch is always on a SNAPSHOT release, and the feature branch(es) should also be in a snapshot version although you may choose to change it to something that does not clash with the develop one - if necessary.

When complete, the feature branch should be a new MR for develop and this will merge changes back to the develop branch 👌

Preparing for release

Develop branch should be merged to master, and a new version using mvn versions:set / mvn versions:commit should be committed to the master branch. When this is done and the build action is successful, the new release should be created via the "Releases -> Create new Release" out of the master branch and a new tag which should be the same as the version used in master now e.g. 1.2.0

When the release is published, github actions will automatically build the tag and publish it to the Github Packages repository.

Updating the develop branch

When the release is complete, make sure that the develop branch gets a new -SNAPSHOT version to continue the process.

Summary

Before release:

• develop is 1.2.0-SNAPSHOT
• feature branch feature/selenium10 is 1.2.0-SNAPSHOT
• master is 1.1.0

After release:

• develop is 1.3.0-SNAPSHOT
• feature branch feature/selenium10 is 1.2.0-SNAPSHOT
• master is 1.2.0