doc: Explicit statement of developer-level support
What does this MR do and why?
Clarify what Developer support means, within the Maintenance policy, so as to differentiate Support's engagements from that of the developer teams.
Debugging (self-hosted) customer issues on ancient versions is a significant burden and opportunity cost on engineering teams. Since we would not backport any fixes to old versions, there's no point in engaging there (but if the issue were still present in new versions, we will engage and fix).
Issue: https://gitlab.com/gitlab-com/Product/-/issues/13235+s
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.