Aluminium Formal Release Checklist

Communicate code freeze to projects

DoneJul 29, 2020 

1 weeks before code freeze happens

@Daniel De La Rosa

Code freeze (stable branch lock)

Done Aug 4, 2020 

1 weeks before any release.

@Anil Shashikumar Belur

Pick RC and produce CSIT spreadsheet

Done Sep 11, 2020 

All blocker bugs must be closed before picking the RC. This is tentative date.

@Daniel De La Rosa @JamO Luhrsen

Vet CSIT failures

Done Sep 15, 2020 

Max 1 week after CSIT spreadsheet is shared 

all projects

TSC votes the Managed release

DoneSep 17, 2020 

TSC

Remind PTL to produce release notes (only for GA release)

Done Sep 17, 2020 

release manager

Publish released artifacts to Nexus

Done Sep 17, 2020 

@Anil Shashikumar Belur

Communicate Managed release to Self Managed projects

Done Sep 17, 2020 

@Daniel De La Rosa

Unlock stable branch

Done Sep 17, 2020 

@Anil Shashikumar Belur

Release All SM projects (including "official" distribution)

Done  Sep 22, 2020 

Max 1 week after Managed release.

All SM projects (including int/dist)

Update docs

Done  Sep 25, 2020 

• downloads page

• managed projects

• Platform Versions Page

• release notes

  • release notes job (only for service releases) (jira to do this for major release). For GA projects PTLs have to push patch to docs.

• Main landing page

  • Make sure the Managed projects and Self-managed project lists are up to date.

Branch docs project ( Only for GA release )

Done Sep 25, 2020 

• on master branch bump versions to next release (conf.yaml)

  • Clear per-project release notes in master to prep for next release

• on new stable/branch update links to stable/branch away from "latest" (conf.py)