Skip to content

Instantly share code, notes, and snippets.

@briceburg

briceburg/versioning-and-releases.md

Last active December 8, 2021 16:29
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save briceburg/6c84af5fa32332d5e3a179642d6f0850 to your computer and use it in GitHub Desktop.
Save briceburg/6c84af5fa32332d5e3a179642d6f0850 to your computer and use it in GitHub Desktop.
Download ZIP
eight bullet versioning and release process
Raw
versioning-and-releases.md

releases

  • semantic versioning is used
  • a branch is created for every major release, e.g. release-1.x, release-2.x, &c.
  • when ready to make a release;
    • update any changelogs and documentation with release information, commit/merge to main. ensure CI passes.
    • if backporting fixes into past releases, follow the backporting procedure from containerd, else merge main into the current release branch. e.g. main -> release-2.x.
    • checkout current release branch and update files/version with the current point release, e.g. change 'main' to 2.1.18-rc1.
      • make a release commit (e.g. with message "RELEASE 2.1.18-rc1").
      • tag the release using v as a prefix, e.g. git tag v2.1.18-rc1 && git push --tags
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment