debian-mirror-gitlab/data/deprecations/templates/example.yml

51 lines
3.2 KiB
YAML
Raw Normal View History

2022-07-23 23:45:48 +05:30
# This is a template for a feature deprecation.
2021-11-11 11:23:49 +05:30
#
2022-10-11 01:57:18 +05:30
# Please refer to the deprecation guidelines to confirm your understanding of the
# definitions for "Deprecation", "End of Support", and "Removal":
2022-07-23 23:45:48 +05:30
# https://docs.gitlab.com/ee/development/deprecation_guidelines/#terminology
#
# Deprecations must be announced at least three releases prior to removal.
2022-10-11 01:57:18 +05:30
# See the OPTIONAL END OF SUPPORT FIELDS section below if an End of Support period also applies.
2022-07-23 23:45:48 +05:30
#
# Breaking changes must happen in a major release.
2021-11-11 11:23:49 +05:30
#
# For more information please refer to the handbook documentation here:
2021-12-11 22:18:48 +05:30
# https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations
2021-11-11 11:23:49 +05:30
#
# Please delete this line and above before submitting your merge request.
2022-07-23 23:45:48 +05:30
#
# REQUIRED FIELDS
#
2022-07-16 23:28:13 +05:30
- name: "Feature name" # (required) The name of the feature to be deprecated
announcement_milestone: "XX.YY" # (required) The milestone when this feature was first announced as deprecated.
announcement_date: "YYYY-MM-DD" # (required) The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
removal_milestone: "XX.YY" # (required) The milestone when this feature is planned to be removed
removal_date: # (required) The date of the milestone release when this feature is planned to be removed. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
breaking_change: false # (required) If this deprecation is a breaking change, set this value to true
reporter: exampleuser # (required) GitLab username of the person reporting the deprecation
stage: stage # (required) String value of the stage that the feature was created in. e.g., Growth
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/000000 # (required) Link to the deprecation issue in GitLab
body: | # (required) Do not modify this line, instead modify the lines below.
2021-11-11 11:23:49 +05:30
<!-- START OF BODY COMMENT
This area supports markdown. Delete this entire comment and replace it with your markdown content.
2021-12-11 22:18:48 +05:30
When ready, assign to your tech writer for review. When ready, they will run `bin/rake gitlab:docs:compile_deprecations` to update the deprecations doc, then merge.
2021-11-11 11:23:49 +05:30
END OF BODY COMMENT -->
2022-07-23 23:45:48 +05:30
#
2022-10-11 01:57:18 +05:30
# OPTIONAL END OF SUPPORT FIELDS
#
# If an End of Support period applies, the announcement should be shared with GitLab Support
# in the `#spt_managers` channel in Slack, and mention `@gitlab-com/support` in this MR.
2022-07-23 23:45:48 +05:30
#
end_of_support_milestone: # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
end_of_support_date: # (optional) The date of the milestone release when support for this feature will end.
2022-10-11 01:57:18 +05:30
#
# OTHER OPTIONAL FIELDS
#
2022-04-04 11:22:00 +05:30
tiers: # (optional - may be required in the future) An array of tiers that the feature is available in currently. e.g., [Free, Silver, Gold, Core, Premium, Ultimate]
documentation_url: # (optional) This is a link to the current documentation page
image_url: # (optional) This is a link to a thumbnail image depicting the feature
video_url: # (optional) Use the youtube thumbnail URL with the structure of https://img.youtube.com/vi/UNIQUEID/hqdefault.jpg