You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no formal deprecation policy defined in the ORAS community. Some flags/commands hide a deprecated flag immediately but some have explicit deprecated feature mark in the --help information. We may want to align on the deprecation policy and formalize the policies in the ORAS community. This should be a part of feature lifecycle management.
My suggstions:
Soft Deprecation First: When a flag or command is deprecated, show warnings in logs and help text in the current release. Suggest new commands or flags in the warning.
Gradual Removal: Keep deprecated features for multiple versions before removal.
Versioning & Breaking Changes: Use the major version upgrades for entire removals.
Document & Announcement: Clearly list deprecations in release notes and documentation. Announce it in the release blog post.
There is no formal deprecation policy defined in the ORAS community. Some flags/commands hide a deprecated flag immediately but some have explicit deprecated feature mark in the
--helpinformation. We may want to align on the deprecation policy and formalize the policies in the ORAS community. This should be a part of feature lifecycle management.My suggstions:
Linking to another corresponding issue: #199
The text was updated successfully, but these errors were encountered: