10/30/20 Patch Releases (+k3s2 releases)

[davidnuzik]

Summary:
Task covering patch releases work. These releases are not coming from upstream, they include bugfixes and improvements. v1.19.3+k3s2 will include fixes from the master branch as well as support for RHEL8. Refer to the release notes for more information once it is available.

List of required releases:
To release as soon as able for QA:
v1.17.13-rc1+k3s2 (RC needed for KDM testing in Rancher)
v1.18.10-rc1+k3s2 (RC needed for KDM testing in Rancher)
v1.19.3-rc1+k3s2 (RC needed for KDM testing in Rancher)

To release once have approval from QA:
v1.17.13+k3s2
v1.18.10+k3s2
v1.19.3+k3s2

Prep work:

• PM: EIO team notified of the incoming releases - send calendar invite
• PM and QA: Review changes and understand testing efforts
• Menna: Prep PR for rancher/kontainer-driver-metadata (bump patch versions)
• PM: Draft Releases (fill in release notes, mark as pre-release, fill in title, set target release branch, leave tag version blank, save as draft)
• QA: Validate and close out all issues in the release milestone.

Vendor and release work:

• Brad: Vendor in new patch versions into the appropriate branches and release rancher/kubernetes
• PM: Merge PR for rancher/kontainer-driver-metadata into the dev branches
• Brad: Tag and release any necessary RCs for QA to test KDM
• Brad: Tag and release the K3s patches when have QA and PM approval

Post-Release work:

• Brad: Once all releases are complete and all release artifacts exist, uncheck "Pre-release" for each
• PM: Mark the latest v1.19.x release as stable (this is done typically at least 7 days post release in a separate GH issue.)
• Rancher PM: (handled separately offline) Merge in rancher/kontainter-driver-metadata change to release branch (so new patch versions show up as upgrade options in Rancher UI)