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.
As it is, even for short projects we end up having to stay on whatever version of Django we started with because the client won't pay for the work required to upgrade. Then each version that gets released is yet more work that needs done, so the estimate to update gets larger and larger every six months. The net effect is we get stuck on older versions unable to take advantage of those new features anyhowways. On Saturday, April 4, 2015 at 7:30:59 AM UTC-5, Tim Graham wrote: > > Now that Django 1.8 is released, I wanted to bump this thread for > discussion so we can hopefully ratify this schedule or modify it based on > feedback. In particular, I heard a concern that a six month release > schedule may be too often for the community. On the other hand, I think > smaller releases would make incremental upgrades easier. > > One difficulty could be if third-party packages try to support every > version since the last LTS (this seemed to be common with 1.4). A 6 month > release schedule would mean 5 versions of Django until the next LTS, > instead of 3 as we had since 1.4, so more `if DJANGO_X_Y` conditionals. One > idea is that third-party packages could declare their own "LTS" versions > (if needed) and drop support for older versions more freely in future > development. > > On Wednesday, March 11, 2015 at 8:13:11 PM UTC-4, Tim Graham wrote: >> >> With the release of 1.8 coming up, it's time to think about 1.9! I've >> suggested some dates below. The schedule is similar to the intervals we >> used for 1.8 with the final release date planned for about 6 months after >> 1.8 final (barring unforeseen delays, 1.8 will be released about 7 months >> after 1.7). Please voice any thoughts or concerns. With this schedule it >> seems that any GSoC work would likely be included in 2.0. If you have any >> big features planned, please add them here: >> https://code.djangoproject.com/wiki/Version1.9Roadmap >> >> July 20 - Alpha (feature freeze) >> August 21 - Beta (only release blockers fixed after this) >> September 18 - RC (string freeze for translations) >> October 2 - Final >> > -- 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/9d472e86-2f2c-4e20-8c77-17b3be5e2a1e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
