You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
ℹ️ Team Phoenix is drafting AWS v19.3.2 with Kubernetes v1.24 support.
Target release date: 2024-02-29.
Release PR: ...
Scope
Testing
Pre-Release
README.md
in the release directory.Releasing
Instructions
release.yaml
file.state
toactive
.state: deprecated
). Verify with PO if you have doubts.Example PR
Post-Release
The text was updated successfully, but these errors were encountered: