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.

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

WC Release 19.1.0 on AWS #2713

Closed
4 tasks done
T-Kukawka opened this issue Aug 9, 2023 · 0 comments
Closed
4 tasks done

WC Release 19.1.0 on AWS #2713

T-Kukawka opened this issue Aug 9, 2023 · 0 comments
Assignees
Labels
provider/aws Related to cloud provider Amazon AWS team/phoenix Team Phoenix topic/aws-vintage AWS Vintage Issues

Comments

@T-Kukawka
Copy link
Contributor

T-Kukawka commented Aug 9, 2023

ℹ️ Team Phoenix is drafting AWS v19.1.0 with Kubernetes v1.24 support.
Target release date: 2023-08-21.
Release PR: ...

Scope

Pre-Release

  • Create release ticket on Releases board
  • Make an announcement on #sig-product that team is doing a release. Include a link to the ticket from the release board.
  • Make sure release was tested by creating new cluster, upgrading from older version and with HelloWorld app.
  • Aggregate release notes from all changed components and add to README.md in the release directory.
  • Send draft release announcement to #sig-product for review ASAP.
  • Verify documentation is up to date.

Releasing

  • Create release PR
    Instructions
    • Define new release in release.yaml file.
    • Activate new release by setting state to active.
    • Deactivate old release if it's within same major version (state: deprecated). Verify with PO if you have doubts.
    • Check versions of all components included. They shouldn't be lower than those in the previous release unless there was a rollback.

Example PR

  • Release relevant operators.
    • Tag release branch.
    • Bump operator version in draft release.
  • Make sure that WIP releases in releases repo branch are removed and not merged to master since the master branch is deployed automatically after merging PR and that would make WIP releases visible in customers’ installations which should generally not happen.

Post-Release

  • Update front-end cluster with the new release.
  • Verify release is available on all installations. You can use this script.
  • Send out release announcement to all customers according to these instructions.
  • PO subscribes to release posts on Slack to get notifications if there are follow-up messages.
  • Close release task on Releases board.

Tasks

Preview Give feedback
  1. priority/high team/cabbage
  2. priority/high team/atlas
    QuantumEnigmaa
  3. priority/high team/turtles
    njuettner
  4. priority/high team/shield
@T-Kukawka T-Kukawka added provider/aws Related to cloud provider Amazon AWS team/phoenix Team Phoenix topic/aws-vintage AWS Vintage Issues labels Aug 21, 2023
@whites11 whites11 self-assigned this Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
provider/aws Related to cloud provider Amazon AWS team/phoenix Team Phoenix topic/aws-vintage AWS Vintage Issues
Projects
None yet
Development

No branches or pull requests

2 participants