-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
pre-merge testing requirements
-
Quality / Stability / Reliability
-
False
-
In Progress
-
0% To Do, 0% In Progress, 100% Done
-
-
-
Done! TY Lyn!!
Need to create stories to account for whatever 'day of' or 'preparing for day of' steps required to actually switch over to pre-merge testing AND the promotion to production steps (+ release notes, removing 'held back' list, etc.)
Generally, steps like:
Before Wed. Promotion:
- code freeze
- ‘sync-branches’
- QE to validate master
- Update to our promotion documentation and/or scripts?
- Do we need a new way to generate/broadcast release notes
[eliran] done - see
OCMUI-3034 - decommision/delete ‘Held Back’ wiki?
[eliran] yes
On Wed. Promotion:
- If all of the above is in place, then on Wed. Promotion we can promote master/Staging ‘as is’ to stable/Production.
After Wed. Promotion:
- Would need to change in GitHub PR’s ‘# Approvers required’ from 2 to 3.
- Would need to add a checklist for QE reviewers.
- Once above is done, we can start officially requiring Pre-Merge testing before merging MRs into staging.