On Sat, Apr 4, 2015 at 12:56 PM, Thomas Tanner <tan...@gmx.net> wrote:
> I think rare LTS releases and frequent (6month) incremental upgrades are > a good compromise. > Third-party packages should support LTS releases and at least the latest > Django version. They may drop support for earlier non-LTS releases. > Either you stick with the LTS release or you go with the cutting edge > with all dependencies. > I'm not advocating for or against more frequent releases, but trying to impose a support policy upon 3rd party packages is not going to work. It would great if they support whatever versions of Django are still supported, but sometimes that takes more time/effort than the maintainer is willing to devote. The number or frequency of releases doesn't matter as much as the content of the releases. Depending on the app, some Django versions are harder to support at the same time. The back-to-back major changes to the Datatbase API forced django-mssql to only support a single Django version with each release. After that change, I was less inclined to backport fixes and even stopped testing against Django 1.4 well before it was out of support. > Advantages of release early, release often are that new features have > more time to mature before a LTS release, you don't have to risk using > the unstable HEAD for new features, and more feedback from users. > > On 04.04.15 14:30, 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. > > -- > 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/552017D7.6020907%40gmx.net > . > 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/CAGdCwBvxx%3DVKUscGQV1v%3DezeRkJVY4VJzDBZd9OaJ5SF9951oA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
