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

Consideration to include a control/requirement for a Deprecation Policy to support EoL/EoS #6

Open
camaleon2016 opened this issue Nov 8, 2023 · 0 comments

Comments

@camaleon2016
Copy link

To better mitigate the risks of EoL/EoS for the more critical dependencies, including a control/requirement, or at the very least, part of any proposed maturity model. the establishment of a Deprecation Policy. More critical dependencies could take years to properly deprecate prior to EoL/EoS. Having a policy in place helps to ensure ease of deprecation and then migration to the newer version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant