Skip to content

release: v20.0.0 — general availability - #25

Draft
prateekgsingh wants to merge 1 commit into
mainfrom
release/v20.0.0
Draft

prateekgsingh wants to merge 1 commit into
mainfrom
release/v20.0.0

Conversation

@prateekgsingh

Copy link
Copy Markdown
Collaborator

C7 — the GA release (draft until the day-4 soak check on Tue 24 Nov and the owner's go)

  • VERSION → 20.0.0; terraform/versions.tf module name likewise (the tests hold file = config = Terraform = newest notes heading).
  • RELEASE_NOTES.md: ## v20.0.0 — General availability — the rc.2 section folded in; the narrative states the two candidates, the five-day unattended soak and the scale run; upgrade notes for the tag (TAG=v20.0.0, ?ref=v20.0.0), the SCHEDULES upgrade path, the retirement of beta/dev (archived as tags) and the retroactive tags.
  • docs/roadmap.md: the v20 row reads Shipped, with A6 and the deploy-script fix added.
  • README: the release badge no longer counts pre-releases.

No code change. Suite 1,348 passed + 1 skipped; tools/release_notes.py 20.0.0 renders the section the workflow will publish.

After merge (Tuesday): git tag -a v20.0.0 <merge commit> -m "v20.0.0" && git push origin v20.0.0 → release.yml publishes the Release (not a pre-release); build from the tag; canaries; canary e2e; promote on the owner's go; production e2e; the three deployment methods from the tag.

VERSION 20.0.0, the Terraform provider module name, the release-notes section
renamed from the candidate's (the rc text folded in; the soak and the scale run
stated), the upgrade notes for the tag, the roadmap row Shipped, the README
release badge without pre-releases.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant