Skip to content

Latest commit

 

History

History
43 lines (40 loc) · 3.44 KB

release_issue.md

File metadata and controls

43 lines (40 loc) · 3.44 KB

Release {version}

  • Review closed issues have appropriate tags.
  • Review closed issues have been applied to the current milestone.
  • Ensure the next version milestone is created.
  • Any issues in the current milestone that are not closed, move to next milestone.
  • Run make gen-changelog to generate the CHANGELOG.md (if release candidate make gen-changelog RELEASE_VERSION={version}-rc)
  • Ensure the helm tag value is correct (should be the {version} if a full release, {version}-rc if release candidate)
  • Ensure the helm Chart version values are correct (should be the {version} if a full release, {version}-rc if release candidate)
  • Run make gen-install
  • Ensure all example images exist on gcr.io/agones-images
  • If full release, update documentation with updated example images tags
  • If RC release, update all ⚠️⚠️⚠️ warnings to: "This is currently a release candidate feature"
  • If full release, remove all instances of "⚠️⚠️⚠️ This is currently a development feature and has not been released ⚠️⚠️⚠️"
  • If full release, update install docs with the new release version
  • Create PR with these changes, and merge them with approval
  • Confirm local git remote upstream points at git@github.com:GoogleCloudPlatform/agones.git
  • Run git checkout master && git reset --hard upstream/master to ensure your code is in line with upstream (unless this is a hotfix, then do the same, but for the the release branch)
  • Run make do-release. (if release candidate make do-release RELEASE_VERSION={version}-rc) to create and push the docker images and helm chart.
  • Do a helm repo add agones https://agones.dev/chart/stable and verify that the new version is available via the command helm search agones/
  • Do a helm install and a smoke test to confirm everything is working.
  • Create a release with the release template
    • Make a tag with the release version.
    • Attach all assets found in the release folder to the release.
  • Send an email to the mailing list with the release details (copy-paste the github release)
  • If full release, then increment the base_version in build/Makefile
  • Ensure the helm tag value is set to the next version (should be the {version} if a full release, {version}-rc if release candidate)
  • Ensure the helm Chart version values is set to the next version (should be the {version} if a full release, {version}-rc if release candidate)
  • Run make gen-install
  • Create PR with these changes, and merge them with approval
  • Close this issue.
  • If full release, close the current milestone. Congratulations! - the release is now complete! 🎉 👏 😄 👍