Draft: Create an RSS feed for Breaking Changes
Why is this change being made?
Related to &1916
This MR implements a basic RSS feed which would allow customers to subscribe and receive push notifications about upcoming workflow disruptions.
We received ample feedback in 15.0 that customers needed a better way to review deprecations, removals, and breaking changes. The current process of expecting them to pull notifications by visiting the release post or Docs is insufficient.
Implementation and follow-up
This feed would be a very simple implementation that could be generated via an API call to gitlab-org/gitlab
on a nightly/weekly/monthly basis.
-
Develop a simple task to collect breaking changes from the gitlab
repo, or -
Add a task to manually update the feed during the release post publication process
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - 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 DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.