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

Update deprecation for {{-in-element}} to be until: 3.25.0. #18928

Merged
merged 1 commit into from
Apr 24, 2020

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Apr 24, 2020

We can always delay removal until the community has fully migrated, but having the deprecation be through two LTS (master will be 3.20, then another LTS in 3.24) is more than enough for a private API.

/cc @simonihmig @chancancode

We can always delay removal until the community has fully migrated, but
having the deprecation be through two LTS (master will be 3.20, then
another LTS in 3.24) is more than enough for a private API.
Copy link
Contributor

@simonihmig simonihmig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't sure we are really going to see so many minor releases in the 3.x cycle, but if that's the case this seems reasonable!

@rwjblue
Copy link
Member Author

rwjblue commented Apr 24, 2020

@simonihmig yeah, honestly I don't think we have any clue how many we will have. If 4.0 ends up happening first that seems totally fine to me too...

@rwjblue rwjblue merged commit f0883d6 into master Apr 24, 2020
@rwjblue rwjblue deleted the change-in-element-deprecation-timeline branch April 24, 2020 18:40
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

Successfully merging this pull request may close these issues.

4 participants