-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Announce planned 4.0 deprecations #7800
Comments
The discussion of what to remove in 4.0 is happening at #6792. Note that there are likely things we want to change — not removing functionality, but changing the way to achieve the same functionality. But we don't particularly need to deprecate the old version in advance for that (although we certainly can, and given the number of things we want to change in 4.0 we should get started on those early). |
See also #8663 for a (provisional) list of things we want to make internal, which should be announced as well (from a user's point of view, it's the same as a removal). |
|
For 3.x, we missed the ball and never announced any of the deprecations. For 4.0, we've sent consultation emails. I expect that we'll send other messages once we've made decisions, but there's no particular timeline on announcements. Some aspects of the 4.0 design will not be finalized until March 2025, when we plan remaining changes based on the available time. So I consider this issue to be done. |
Mark things as deprecated in 3.x, so that we can remove things in 4.0.
This issue needs a list of what exactly we will deprecate before we can work on it; for now it's a placeholder.
The text was updated successfully, but these errors were encountered: