This looks like a good plan to me. The main reason for shortening it before as far as I could tell was the lengthy alpha to final process, which hasn't happened this time and hopefully will be rather less frequent in future.
Marc On 7 April 2015 at 00:21, Tim Graham <timogra...@gmail.com> wrote: > With a 9 month schedule, here is what the future might look like: > > 1.8 - April 2015 > 1.9 - January 2016 > 2.0 - October 2016 > 2.1 - July 2017 (LTS, and might be the last version to support Python 2.7 > since 3 years of LTS support would cover until the 2020 sunset.) > 2.2 - April 2018 > > Do you think there would be any value in putting together a short survey > for the community to get a wider consensus? > > > On Monday, April 6, 2015 at 5:30:40 PM UTC-4, Shai Berger wrote: >> >> 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. >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/56675028-6c26-4f72-9491-98f2db0f529e%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/56675028-6c26-4f72-9491-98f2db0f529e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1FBi1f1wOYXAThzT0OfZt9JekO5g53jcy5uOtn%2B9uw58g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
