Skip to content
This repository was archived by the owner on Feb 22, 2022. It is now read-only.

Versioning

Jump to bottom
Ryan Riley edited this page Oct 23, 2015 · 1 revision

Semver

Freya follows semver:

  • Breaking changes bump the major version
  • Non-breaking changes that constitute new features bump the minor version
  • Bug fixes bump the fix version

All Freya components are versioned together, so a change to one of the libraries bumps the version for all libraries, regardless of whether or not the other libraries changed.

Release Versions

Freya now uses tags to identify release versions. When a tag is built in our public AppVeyor CI, the top-most version number found in RELEASE_NOTES.md is used as the release version, and AppVeyor publishes the built packages to NuGet.

Once a commit has been tagged as a release using git tag 1.2.3, where 1.2.3 is the release version, the tagger should add a new target release version to the RELEASE_NOTES.md file and commit that update to the master branch. This can be committed with the [skip ci] instruction to prevent generating an unnecessary build.

Build (Beta) Versions

All commits to master will generate a push to NuGet via our AppVeyor CI. Build, or beta, versions have a suffix of -b123 where 123 is the build number. These show up as pre-release versions in the public NuGet feed.

Clone this wiki locally