Skip to content
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

Spell out deprecation policy #1249

Closed
marquiz opened this issue Jun 22, 2023 · 3 comments · Fixed by #1279
Closed

Spell out deprecation policy #1249

marquiz opened this issue Jun 22, 2023 · 3 comments · Fixed by #1279
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@marquiz
Copy link
Contributor

marquiz commented Jun 22, 2023

What would you like to be added:

Spell out (in the documentation) a deprecation policy for NFD. E.g.

  • feature labels must be supported for 2 more releases after deprecation (i.e. if label is deprecated in N, it must be supported in N+1 and N+2 and may be dropped in N+3 the earliest)
  • command line flags must be supported for 1 more release after deprecation

Why is this needed:

Easy for users and the maintainers to understand the expectations.

@marquiz marquiz added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 22, 2023
@marquiz
Copy link
Contributor Author

marquiz commented Jul 21, 2023

See #1279

@marquiz
Copy link
Contributor Author

marquiz commented Jul 21, 2023

@marquiz
Copy link
Contributor Author

marquiz commented Jul 24, 2023

#1283 for Helm charts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants