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.
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.
