Update remaining <pubdate>s in the Breaking Changes RSS feed
Why is this change being made?
!115806 (merged) updated the contents of the XML file on 2022-12-01 but the <pubdate>
for the items was 2022-11-22 (the date of the announcement milestone).
This created an issue where the RSS feed reader in Slack did not post the updated items.
The <pubdate>
needs to be the date the XML is updated, not the milestone announcement date in the .yml
source file which was used by default.
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.
Edited by Brian Rhea