Development

Versioning:

Rover follows the Semantic Versioning schema: https://semver.org/

Tagging/branching model:

• Major releases are always tagged on master. Minor releases to the latest major release as well.
• Bug fixes and feature development to the current major version are done on the master branch.
• If bug fixes or feature back ports are needed for an older major version release, a branch will be created at the release tag. New minor releases to that branch are tagged on that branch.

The development cycle is as follows:

• Changes are created in a pull request against master, or an older major release branch.
• Changes are reviewed by another committer, with explicit approval noted in the PR comments.
• The PR is merged by any committer. Usually with all commits squashed, with a concise message.

Cutting releases:

Once a release stage is agreed upon, but a new release according to the steps on the Maintainer page.