-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
pre-merge testing requirements
-
True
-
-
False
-
To Do
-
OCMUI-2062 - Pre-Merge Testing & Updated Promotion Process
-
OCMUI-2062Pre-Merge Testing & Updated Promotion Process
-
0% To Do, 0% In Progress, 100% Done
-
-
-
(10/22) mortegag: finishing some tasks. I think next week will be available.
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?
- decommision/delete ‘Held Back’ wiki?
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 GitLab MR’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.