Skip to content

Versioning

Andy edited this page Apr 3, 2020 · 4 revisions

Versioning in Atlantis follows standard practices:

<major>.<minor>.<patch>-<dev>

Each increment is defined as follows:

<patch> e.g. from 1.5.3 - 1.5.4

A patch is used to fix bugs or make minor changes. No new features are added under a patch release.

For Atlantis these equate to:

  • Parameter changes
  • Processing (pre/post) R script changes/additions

<minor> e.g. from 1.5.4 - 1.6.0

A minor release is used when new features have been added that are backward compatible.

  • Update forcing files
  • Update fleet structure

<major> e.g. from 1.6.0 - 2.0.0

A major release is used for changes that are not backward compatible. Changes that would break previous versions.

  • Box structure changes
  • Functional group changes
  • Addition of New module (???)

<dev> e.g. 1.5.3-9000

A dev change is one that hasn't been released. It is a change that is still in development. These changes can be any of the above mentioned changes. However the type of change will determine the next full release.

All version and development updates are documented in news.md with associated pull request numbers

For more info on semantic versioning (semver.org)