3 ms·
Is the Django team planning anything big for a 2.0 release?
by snogglemedia 11y ago
Is the Django team planning anything big for a 2.0 release?
- ubernostrum 11y agoExpanding a bit: the plan is that 2.0 just switches us to a new versioning system. The tl;dr is: Versions start going 2.0, 2.1, 2.2, then 3.0, 3.1, 3.2, then 4.0, 4.1, etc. Every X.2 is a long-term support release. The deprecation cycle gets tweaked so that if you're on, say, 2.2 LTS and your codebase runs with no deprecation warnings, then you'll be able to just run as-is on 3.2 LTS. You can then clean up any deprecation warnings on 3.2, and you'd be good to go for 4.2 LTS, etc.
- Scarblac 11y agoAnd as a special case of that: according to the current roadmap, 1.11 will be the last version to support Python 2.7, 2.0 won't.
- minimaxir 11y agoNot for a couple years: https://www.djangoproject.com/weblog/2015/jun/25/roadmap/ https://www.djangoproject.com/weblog/2015/jun/25/roadmap/
- jsmeaton 11y agoNo, not really. Django is moving to an "almost semver" versioning system. The X.0 releases will be when deprecated features are actually removed. There are still some big ticket features that various people want to work on. These get released as they become ready. There may be some feature that is targeted for 2.0, but we won't know what until after 1.11.
- ponytech 11y agoThe integration of Andrew Godwin's django channels [1] would be a big thing :) [1] https://github.com/andrewgodwin/channels https://github.com/andrewgodwin/channels