-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Removed Table for deprecation.md #6209
Conversation
Skipping CI for Draft Pull Request. |
100467a
to
44b222a
Compare
44b222a
to
8bf828b
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
d519b8a
to
7651f84
Compare
995fa8d
to
50eb551
Compare
I thought |
Good question! This came from the reason that #6206 (comment) suggests we should not remove deprecated fields from deprecation table. While EOL in the above table indicates the time that we could remove it, the new table targets to note down the time it was actually removed and the latest supporting LTS for that feature. |
@abayer @afrittoli @bobcatfish @jerop @lbernick please take a look at the PR to take a decision on it 👼🏼 |
37ca0b3
to
5a96e88
Compare
This commit updates the deprecation.md by creating a 'removed' table to distinguish the features that are removed or being deprecated.
ce067c8
to
56901ec
Compare
/retest |
/retest |
Changes
This commit updates the deprecation.md by creating a 'removed' table to
distinguish the features that are removed or being deprecated.
/kind documentation
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes