Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release 1.16.0-rc #2179

Closed
63 tasks done
roberthbailey opened this issue Jul 13, 2021 · 2 comments
Closed
63 tasks done

Release 1.16.0-rc #2179

roberthbailey opened this issue Jul 13, 2021 · 2 comments
Labels
kind/release Checklist for a release
Milestone
1.16.0

Comments

@roberthbailey
Copy link
Member

roberthbailey commented Jul 13, 2021 •
edited
Loading

Prerequisites

  • Have at least Editor level access to agones-images project.
  • Have write access to Agones github repository.
  • Have a gcloud config configurations configuration called agones-images that points to the same project.
  • Have a Github Personal Access Token with repo permissions.
  • Edit access to the Agones Release Calendar

Steps

  • Run make shell and run gcloud config configurations activate agones-images.
  • Review closed issues with no milestone and add relevant ones to the current milestone.
    • Issues tagged as invalid, duplicate, question, or wontfix can be ignored
  • Review closed issues in the current milestone to ensure that they have appropriate tags.
  • Review merged PRs that have no milestone and add them to the current milestone.
  • Review merged PRs in the current milestone to ensure that they have appropriate tags.
  • Ensure the next RC and stable releases in the Google Calendar have the correct version number.
  • 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 main && git pull --rebase upstream main
  • If full release, run make site-deploy SERVICE=1.16.0-1, (replace . with -)
  • Run make gen-changelog to generate the CHANGELOG.md (if release candidate
    make gen-changelog RELEASE_VERSION=1.16.0-rc). You will need your
    Github Personal Access Token for this.
  • Ensure the helm tag value is correct (should be 1.16.0 if a full release, 1.16.0-rc if release candidate)
  • Ensure the helm Chart version values are correct (should be 1.16.0 if a full release, 1.16.0-rc if release candidate)
  • Update SDK Package Versions
  • 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, add a link to previous version's documentation to nav dropdown.
    • config.toml updates:
      • If full release, update release_branch to the new release branch for 1.16.0.
      • If full release, update release-version with the new release version 1.16.0.
      • If full release, copy dev_supported_k8s to supported_k8s.
      • If full release, copy dev_aks_minor_supported_k8s to aks_minor_supported_k8s.
      • If full release, copy dev_minikube_minor_supported_k8s to minikube_minor_supported_k8s.
      • If full release, update documentation with updated example images tags.
  • Create PR with these changes, and merge them with an approval.
  • Confirm local git remote upstream points at [email protected]:googleforgames/agones.git
  • Run git remote update && git checkout main && git reset --hard upstream/main 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. Requires Google internal process
      to publish.
    • Run make sdk-publish-csharp to deploy to NuGet. Requires login credentials. (if release candidate:
      make sdk-publish-csharp RELEASE_VERSION=1.16.0-rc).
      Will need NuGet API Key from Agones account.
  • Run make do-release. (if release candidate: make do-release RELEASE_VERSION=1.16.0-rc) to create and push the docker images and helm chart.
  • Do a helm repo add agones https://agones.dev/chart/stable / helm repo update and verify that the new
    version is available via the command helm search repo agones --versions --devel.
  • Do a helm install --namespace=agones-system agones agones/agones
    (helm install --namespace=agones-system agones agones/agones --version=1.16.0-rc if release candidate) and a smoke test to confirm everything is working.
  • Attach all assets found in the release folder to the draft Github Release.
  • Publish the draft Github Release.
  • Send an email to the mailing list with the release details (copy-paste the release blog post)
  • Paste the announcement blog post to the #users Slack group.
  • Post to the agonesdev twitter account.
  • If full release, run git checkout main.
  • If full release, then increment the base_version in build/Makefile
  • If full release move helm tag value is set to 1.16.0+1-dev
  • If full release move the helm Chart version values is to 1.16.0+1-dev
  • If full release, change to the sdks/nodejs directory and run the command npm version 1.16.0+1-dev to update the package version
  • If full release move the sdks/csharp/sdk/AgonesSDK.nuspec and sdks/csharp/sdk/csharp-sdk.csproj to 1.16.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! 🎉 👏 😄 👍
@roberthbailey roberthbailey added the kind/release Checklist for a release label Jul 13, 2021
@roberthbailey roberthbailey added this to the 1.16.0 milestone Jul 13, 2021
markmandel pushed a commit to markmandel/agones that referenced this issue Jul 13, 2021
@WeetA34 @markmandel
Fix Rust Sample Docker image
13f99ba 
Looks like the Docker image and accompanying build scripts weren't
updated with the move to Tonic, so it all went 💥.

This fixes that, removing lots of dependencies we no long need (yay
Tonic), upgrading the Rust version, and making sure all the relevant
code (e.g. protos) are copies to the appropriate place when creating the
Docker build image.

Work on googleforgames#2179
@markmandel markmandel mentioned this issue Jul 13, 2021
Merged
markmandel added a commit to markmandel/agones that referenced this issue Jul 13, 2021
@markmandel
Fix Rust Sample Docker image
0a1d3fc 
Looks like the Docker image and accompanying build scripts weren't
updated with the move to Tonic, so it all went 💥.

This fixes that, removing lots of dependencies we no long need (yay
Tonic), upgrading the Rust version, and making sure all the relevant
code (e.g. protos) are copies to the appropriate place when creating the
Docker build image.

Work on googleforgames#2179
roberthbailey pushed a commit that referenced this issue Jul 13, 2021
@markmandel
Fix Rust Sample Docker image (#2180)
fb52741 
Looks like the Docker image and accompanying build scripts weren't
updated with the move to Tonic, so it all went 💥.

This fixes that, removing lots of dependencies we no long need (yay
Tonic), upgrading the Rust version, and making sure all the relevant
code (e.g. protos) are copies to the appropriate place when creating the
Docker build image.

Work on #2179
@roberthbailey
Copy link
Member Author

@markmandel - please let me know once you've posted to twitter and we can mark this as complete.

@markmandel
Copy link
Member

Done!
https://twitter.com/agonesdev/status/1415370944260964352

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/release Checklist for a release
Projects
None yet
Milestone
1.16.0
Development

No branches or pull requests
2 participants
@markmandel @roberthbailey