THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Enjoy an adult beverage (or bubble tea) of your choice, and congratulations on making a MXNet release.
The Release Checklist Template
For Every Release you must use the following checklist to ensure that all tasks happen in a timely manner -
In case you need to update this list, the original spreadsheet is here(https://docs.google.com/spreadsheets/d/1i75E7XHb4hqOebhygvUJWJngJzZPwOoI8HPBqdvWUBU/edit#gid=0)
| Task # | Task | Owner | Relative Date | Absolute Date |
| PreReqs for Release Start: | PM | |||
| 1 | Finalize the Release Date | PM | T-15 | |
| 2 | High Level List of Features and artifact specs | PM | T-15 | |
| 3 | Prepare Release Notes - draft 1 | PM | T-15 | |
| 4 | Inform the community | Release Committer | T-15 | |
| 5 | PR to update the Website into master/RB | WebsiteLead | T-14 | |
| 6 | PR to update the Docs into master/RB | DocsLead | T-14 | |
| 7 | PR to update the versions into master/RB | ReleaseLead | T-14 | |
| 8 | Validate Licenses (how? Apache RAT and?) | ReleaseLead | T-14 | |
| 9 | Validate/update submodules | ReleaseLead | T-14 | |
| 10 | Stabilize the code for CI to pass | ReleaseLead | T-14 | |
| 11 | Merge all necessary PRs into master | Community | T-13 | |
| 12 | Code Freeze and Release Start: Cut the Release Branch | Release Manager | T-10 | |
| 13 | Finalize the Release Notes based on PRs that got in - final draft | PM | T-10 | |
| 14 | PR to update the NEWS and README into the RB | ReleaseLead | T-9 | |
| 15 | validate the docs build locally (how?) | DocsLead | T-9 | |
| 16 | Test part 1: Run the unit Tests on the Release Branch | ReleaseLead | T-8 | |
| 17 | Test part 2: Run the Nightly Tests | ReleaseLead | T-8 | |
| 18 | Create the Github Tag for the rc0 | Release Committer | T-7 | |
| 19 | Create the src tar and sign, Upload the src tar | Release Committer | T-7 | |
| 20 | Validate the signatures | Release Lead | T-7 | |
| 21 | Clone svn repo and do a manual test | Release Lead | T-7 | |
| Begin Apache Voting | Release Committer | T-7 | ||
| 22 | Start the vote on devl@ | |||
| 23 | Send out the results of the vote on dev@ | Release Committer | T-4 | |
| 24 | Revote if necessary (Steps 15-22) | Release Committer | Not Accounted For | |
| 25 | Start the vote on general@ | Release Committer | T-4 | |
| 26 | Send out the results of the vote on general@ | Release Committer | T-1 | |
| End Apache Voting | ||||
| 27 | Create the final release tag on github | Release Committer | T-1 | |
| 28 | Rename, resign and upload the src tar to final dir | Release Committer | T-1 | |
| 29 | Update the website using tag | Website Lead | T-1 | |
| 30 | Release the official pip package | pip Lead | T-1 | |
| 31 | Release the official docker images | Docker Lead | T-1 | |
| 32 | After 24 hrs, validate the packages are uploaded | Release Lead | T | |
| 33 | Draft the offical announce email and review | Release Committer | T-1 | |
| 34 | Send out the email on announce@ | Release Committer | T | |
| 35 | Update the apache blog | Release Committer | T | |
| 36 | update the aws blog | PM | T | |
| 37 | send internal announcement | PM | T | |
| 38 | Update the version on master | Release Lead | T+1 |
...