Skip to content

Update deprecations to have planned removal date

Mark Wood requested to merge fix-deprecation-date into master

Why is this change being made?

From the GitLab Release Post %13.12 Retrospective - #11579 (comment 579535325)

Currently, deprecations in release posts contain the text Deprecation date: for every entry. This appears incorrect, since what we're really doing is announcing when we plan the removal to take place.

This MR will update that text for release posts to instead read Planned removal date: which should clarify that the deprecation notice is announcing something planned for the future, and will clearly communicate the planned removal date.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct 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 in 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 changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)

Merge request reports