Geo staging failover planning and execution target date
Why is this change being made?
Suggesting a more ambitious target for a failover on staging, with addition that it has to remove disruption as much as possible.
The reason for this new target is that we have a Production Change Lock during 26th and 27th, which is the perfect time to execute testing on staging as this would have smaller impact on the regular production processes.
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what -
Assign this change to the correct DRI - If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
- If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping
@gl-static-site-editorin a comment for a review and merge. For example changes to.gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.