Delayed maturity increase
Why is this change being made?
- We have not yet delivered two major features that improve planned failovers (gitlab-org&2159 (closed) and gitlab-org&2149 (closed))
- We are working on a self-service framework to accelerate adding and verifying data to Geo but we still need to add significant amounts of data to Geo see https://docs.gitlab.com/ee/administration/geo/replication/#current-limitations
- We have to simplify the failover process in an iterative fashion
The team is focused on this but given the above we should delay the maturity increase until the end of Q2.
Does this MR meet the acceptance criteria?
Assign to DRI
-
Did you assign this change to the correct DRI of the page or information you are changing?
Conformity
-
Added description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
Edited by Fabian Zimmer