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

Cut 1.19.14 #1548

Closed
4 of 11 tasks
fapatel1 opened this issue Aug 5, 2021 · 0 comments
Closed
4 of 11 tasks

Cut 1.19.14 #1548

fapatel1 opened this issue Aug 5, 2021 · 0 comments
Assignees
@briandowns
Labels
area/release
Projects
Development [DEPRECATED]
Milestone
v1.19.14+rke2r1

Comments

@fapatel1
Copy link

fapatel1 commented Aug 5, 2021 •
edited by briandowns

To release as soon as able for QA:

  • v1.19.14-rc1+rke2r1

To release once have approval from QA:

  • v1.19.14+rke2r1 (Never release on a Friday unless specified otherwise)

Prep work:

  • PM: Dev and QA team to be notified of the incoming releases - send calendar invite
  • PM: Dev and QA team to be notified of the date we will mark the latest release as stable - send calendar invite
  • QA: Review changes and understand testing efforts
  • Release Captain KDM Work: Merge PR for rancher/kontainer-driver-metadata into the dev branches
  • Release Captain: Prepare release notes in our private release-notes repo (submit PR for changes taking care to carefully check links and the components, once merged, create the release in GitHub and mark as a draft and check the pre-release box, fill in title, set target release branch, leave tag version blank for now until we are ready to release)
  • QA: Validate and close out all issues in the release milestone.

Vendor and release work:

  • Release Captain: Tag and release any necessary RCs for QA to test KDM
  • Release Captain: Tag and release when have QA approval

Post-Release work:

  • Release Captain: Once release is fully complete (CI is all green and all release artifacts exist), edit the release, uncheck "Pre-release", and save.
  • Release Captain: Prepare PRs as needed to update KDM in the appropriate dev branches.
  • PM: Close the milestone in GitHub.
@fapatel1 fapatel1 added this to To Triage in Development [DEPRECATED] via automation Aug 5, 2021
@fapatel1 fapatel1 moved this from To Triage to Next Up in Development [DEPRECATED] Aug 5, 2021
@fapatel1 fapatel1 added this to the v1.19.14+rke2r1 milestone Aug 5, 2021
@briandowns briandowns moved this from Next Up to Working in Development [DEPRECATED] Aug 17, 2021
@briandowns briandowns moved this from Working to Done Issue / Merged PR in Development [DEPRECATED] Aug 27, 2021
@cwayne18 cwayne18 closed this as completed Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@briandowns briandowns

Labels
area/release
Projects
No open projects
Development [DEPRECATED]
Done Issue / Merged PR
Milestone
v1.19.14+rke2r1
Development

No branches or pull requests
3 participants
@cwayne18 @briandowns @fapatel1