Consider reducing Release Manager workload by dropping some testing for rollbacks
Problem Statement
Currently the Release Manager workload is slated to increase due to: https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/2645. Due to this, I'd like to suggest that we modify the timing for testing, or maybe the policy for how we consider that rollback testing is validated. Doing so should reduce how much work any given Release Manager is responsible for during their time covering this role.
Considerations
- Reduce the amount of times we test, currently we mandate that we test 3 times on staging - but no tests occur on production - I'd like to reduce this to 2 tests per release milestone
- Aside from staging testing, if we ever perform a rollback successfully in production, this effectively completes this task in it's entirety for that release milestone.
- ...
Milestones
-
Validate this still meets our desired goals - validating that rollbacks works as desired -
Update documentation with any new results of decision made in this discussion