287
edits
Release Management/Release Process Checklist Documentation: Difference between revisions
Release Management/Release Process Checklist Documentation (view source)
Revision as of 10:57, 23 October 2020
, 23 October 2020→Nightly Checklist: there aren't mid-nightly and pre-beta test reports anymore
(→Nightly Checklist: remove reference to nightly deep dive meeting) |
(→Nightly Checklist: there aren't mid-nightly and pre-beta test reports anymore) |
||
| Line 22: | Line 22: | ||
The release manager should also review the test plans for features targeting their releases to become familiar with how the feature works and how we intend to ensure it is of sufficient quality to ship in that release. This also gives an opportunity to provide feedback on the risk analysis and mitigations put in place. | The release manager should also review the test plans for features targeting their releases to become familiar with how the feature works and how we intend to ensure it is of sufficient quality to ship in that release. This also gives an opportunity to provide feedback on the risk analysis and mitigations put in place. | ||
Once | Once Nightly test reports are emailed by QA, the release manager should check the newly-reported bugs to make sure flags are set correctly and the new issues have been addressed by engineering and product teams and prioritized accordingly. Release managers can help make sure that all of the pertinent information is in place to make decisions about whether the feature is ready to ship to Beta or whether it should remain Nightly-only for another cycle for more testing and development. | ||
Near the end of the cycle, the following actions must be performed: | Near the end of the cycle, the following actions must be performed: | ||