Pkl, if you're interested, I'd encourage you to be more involved in the development process including this mailing list when changes are proposed. I'm afraid raising a whole bunch of old issues that have already been discussed and decided isn't that helpful.
Our deprecation policy (as you probably know) is to maintain backwards compatibility (where at all possible) for two releases. Keeping these shims indefinitely, however, would add a lot of complexity and hinder our ability to evolve the framework. I don't believe we've diverged from our API stability policy regarding the deprecation process. As you may know, we have added an experimental "Long Term Support" release (currently 1.4) for projects that don't wish to update to the newest versions of Django as quickly as we put them out. We've also decided that "2.0" will simply be the release following 1.9. It won't be a big backwards incompatible release with sweeping changes. If you have other suggestions to address your concerns let us know. Out of respect for the many volunteers that contribute their time to Django, please consider toning down the grim tone. :-) Tim On Monday, September 1, 2014 5:50:25 PM UTC-4, Collin Anderson wrote: > > I agree that there have been a lot of backwards-incompatible changes over > the last few years clean up the API. We've really been in "get stuff done" > mode. > > I do however think it's a not good idea to break all compatibility in one > single shot. Python 3 did this and 6 years later it's still preventing many > of us from even starting to use it. Spreading out the backwards > incompatibilities over many releases is a very good idea. > -- You received this message because you are subscribed to the Google Groups "Django developers" 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/0fbe4ac0-317b-4a34-8e0e-118b7f39738e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
