This sounds good. But will it significantly slow down the rollout of new features into Django that require deprecation? Also, could features that are deprecated in an LTS be dropped in the next non-LTS release? e.g. if 1.8 still had a feature that was deprecated in 1.5, could it finally be removed in 1.9?
On Friday, May 8, 2015 at 1:53:59 AM UTC+10, Carl Meyer wrote: > > On 05/07/2015 08:53 AM, Tim Graham wrote: > > I think there is some merit to reconsidering the deprecation schedule as > > Anssi suggests. What I have seen is that most third-party apps didn't > > consider dropping support for the previous LTS (1.4) until the next LTS > > (1.8) was released. This meant that all these projects had to implement > > their own compatibility shims (instead of using Django's) once they > > wanted to add support for Django 1.6+ because the compatibility shims > > for deprecated features in 1.4 were dropped in Django. This resulted in > > ugly code with lots of conditional version branches, etc. I'll keep > > thinking about this as we decide the release schedule going forward. > > I agree with this. I think by far the biggest thing we could do to make > it easier to go from LTS to LTS is to make it easier for third-party > apps to support two LTS releases at once. Guaranteeing that no API which > is un-deprecated in one LTS will be removed until after the following > LTS would make that massively easier. > > Carl > > > -- 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/ebcfc899-fe81-481d-9c00-9e66b5967c56%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
