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

Document deprecation process #73

Open
Tracked by #180
mariajgrimaldi opened this issue Mar 8, 2023 · 0 comments
Open
Tracked by #180

Document deprecation process #73

mariajgrimaldi opened this issue Mar 8, 2023 · 0 comments
Assignees
Labels
documentation Relates to documentation improvements

Comments

@mariajgrimaldi
Copy link
Member

Description

As a result of this PR, which adds a filter to a legacy page, we must decide and document a deprecation strategy. How should we monitor this effort?

@felipemontoya suggests:

  • for the page is being removed, I am notified for one stable release
  • when possible, the filter is used in the new replacement page or the API that MFEs call for the same feature. Otherwise a different but equivalent filter exists for the replacement page.

A strategy I agree with, For now, we will track each filter to check which ones are candidates for deprecation, so we can track them better.

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

No branches or pull requests

2 participants