On Monday 06 April 2015 23:34:09 Chris Foresman wrote: > I'm really curious to know if the version to follow 1.9 is planned to be > 2.0 or 1.10. I feel as though 1.x releases have had a lot of major feature > changes. Maybe it's time to start thinking about features in terms of > major, minor, and bugfix/security patch, and start saving major features > for a 2.0 release that could be LTS. In the meantime, minor features could > be added to 1.9, 1.10, 1.11, etc, and breaking API changes should be added > to 2.x, or 3.x, etc. This would make it (IMO) easier to evaluate upgrade > paths, while maintaining the six-month cadence for .x releases of minor > features. > This was decided a little before 1.7 was released: the version after 1.9 will be called 2.0, but it is not going to break things more than earlier releases (there are already warning classes named RemovedInDjango20Warning and RemovedInDjango21Warning in the sources, anticipating the releases after 1.9).
Shai.