17.0 Breaking Changes - Request for additional information
Team @gl-product-pm, we are working to understand the impact of the breaking changes that are coming in 17.0 in partnership with #s_platforms #customer_success and support. PMs, please take a look at this issue.
We have introduced the following breaking change windows in the 17.0
milestone:
-
2024-04-22 09:00UTC
to2024-04-24 22:00UTC
-
2024-04-29 09:00UTC
to2024-05-01 22:00UTC
-
2024-05-06 09:00UTC
to2024-05-08 22:00UTC
We have received a significant amount of reports of customers being surprised by breaking changes and our support organization requires better visibility into when changes are being rolled out. We fully understand that this is a suboptimal, manual mitigation. This is necessary to minimize customer disruption and help support handle incoming tickets.
This is because once you merge or flip the feature flag, things will break for customers on SaaS. That is a huge pain point for support because they have no idea which changes will occur in which windows.
Actions to take
- Check the
GitLab DRI
column for your gitlab username -cmd+f
should work here - Use rich text editing for an easier update to this table
- Please update Column C
Planned Window
with the anticipated merge/enable window. We understand that this is an estimate. - Please update Column D
ROLLED OUT
once all associated MRs with breaking changes are merged.
This is an urgent request. Please complete the Planned Window
by 2024–04-19 17:00 UTC and update the ROLLED OUT
column as soon as it, well, has been rolled out. Communicating potentially disruptive changes to customers is crucial in the lead up to a major release.
A Google Sheet (internal) with more fields for context is also available.
Breaking Changes Table
-
2024-04-22 09:00UTC
to2024-04-24 22:00UTC
- Window 1 -
2024-04-29 09:00UTC
to2024-05-01 22:00UTC
- Window 2 -
2024-05-06 09:00UTC
to2024-05-08 22:00UTC
- Window 3 - N/A - Self Managed Only, no GitLab.com impact