If 5 versions between LTS are too many, what about change LTS interval to 2 years instead 3 years, like Ubuntu, so there are only 3 versions between two LTS versions.
Benefits: - Easier to stick with one LTS instead of catching edge as you are only 1 or 2 versions behind in most time. (If you start a new project just before a new LTS, building against cutting edge so you're on new LTS when your new project is ready!) - Each LTS could still be supported for 3 years, the old LTS version will be supported for 1 more year after next LTS released, users and plugin authors have more time to upgrade their codes. (1 year vs 6 months) - Easier to upgrade to new LTS version since less changes introduced between two LTS versions. - Maximum waiting time for new features go into one LTS version is 18 months instead 30 months. On Saturday, April 4, 2015 at 11:30:59 PM UTC+11, 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 [email protected]. To post to this group, send email to [email protected]. 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/db52498f-d7b4-4c31-a9e0-df246a6115a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
