Release 1.9.0

[markmandel]

• Review closed issues have been applied to the current milestone.
• Review closed issues have appropriate tags.
• Review closed PRs have been applied to the current milestone.
• Review closed PRs have appropriate tags.
• Ensure the next version milestone is created.
• Any issues in the current milestone that are not closed, move to next milestone.
• If release candidate add the label feature-freeze-do-not-merge to any feature pull requests.
• git checkout master && git pull --rebase upstream master
• If full release, run make site-deploy SERVICE=1.9.0-1, (replace . with -)
• Run make gen-changelog to generate the CHANGELOG.md (if release candidate make gen-changelog RELEASE_VERSION=1.9.0-rc)
• Ensure the helm tag value is correct (should be 1.9.0 if a full release, 1.9.0-rc if release candidate)
• Ensure the helm Chart version values are correct (should be 1.9.0 if a full release, 1.9.0-rc if release candidate)
• Update SDK Package Versions
  • Ensure the sdks/nodejs/package.json version is correct (should be 1.9.0 if a full release, 1.9.0-rc if release candidate)
  • Ensure the sdks/csharp/AgonesSDK.nuspec and sdks/csharp/csharp-sdk.csproj versions
    are correct (should be 1.9.0 if a full release, 1.9.0-rc if release candidate)
• Run make gen-install
• Run make test-examples-on-gcr to ensure all example images exist on gcr.io/agones-images-
• Create a draft release with the release template
  • Make a tag with the release version.
• Site updated
  • Copy the draft release content into a new /site/content/en/blog/releases content (this will be what you send via email).
  • Review all link_test and data-proofer-ignore attributes and remove for link testing
  • If full release, review and remove all instances of the feature shortcode
  • If full release, update to the new release branch 1.9.0.
  • If full release, update site with the new release version (release-version in config.toml) to 1.9.0
  • If full release, update documentation with updated example images tags
  • If full release, add link to previous version's documentation to nav dropdown
• Create PR with these changes, and merge them with approval
• Confirm local git remote upstream points at git@github.com:googleforgames/agones.git
• Run git remote update && 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 release branch)
• Publish SDK packages
  • Run make sdk-shell-node to get interactive shell to publish node package
  • Run make sdk-publish-csharp to deploy to NuGet. (if release candidate:
    make sdk-publish-csharp RELEASE_VERSION=1.9.0-rc).
    Will need NuGet API Key from Agones account.
• Run make do-release. (if release candidate: make do-release RELEASE_VERSION=1.9.0-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.
• Attach all assets found in the release folder to the release.
• Submit the Release.
• Send an email to the mailing list with the release details (copy-paste the release blog post)
• If full release, then increment the base_version in build/Makefile
• If full release move helm tag value is set to 1.9.0+1-dev
• If full release move the helm Chart version values is to 1.9.0+1-dev
• If full release move the sdks/nodejs/package.json to 1.9.0+1-dev
• If full release move the sdks/csharp/AgonesSDK.nuspec and sdks/csharp/csharp-sdk.csproj to 1.9.0+1-dev
• If full release, remove feature-freeze-do-not-merge labels from all pull requests
• Run make gen-install gen-api-docs
• 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! 🎉 👏 😄 👍

[markmandel]

Done!