On Mon, Sep 1, 2014 at 9:45 PM, Pkl <[email protected]> wrote: > > Hello, > > I once was once lured to an ideal of long-term stability and > retrocompatibility, by nice docs like this one : > https://docs.djangoproject.com/en/dev/misc/api-stability/ > > But for some years, stuffs have actually been getting worse and worse, with > each django release bringing its little crowd of nightmares. >
Our solution is to not chase releases. Django 1.4 is marked as "Long Term Stable", all our projects use Django 1.4 and no more; if/when a newer stable release is proposed we will consider moving our projects to that. We do then have some problems with 3rd party apps that do not support 1.4.. There was a thread a few weeks ago that discussed (perhaps tangentially) what the next LTS release branch will be, where it was brought up that whatever release it is, the API will actually have to be stable(!), probably ruling out 1.7. So, LTS will probably be 1.4 for some time yet. On Tue, Sep 2, 2014 at 1:48 PM, Aymeric Augustin <[email protected]> wrote: > I'm not sure I understand completely where your frustration comes from. The > tone of your email seems disproportionate with the effort needed to replace > all instances of "django.conf.urls.defaults" with "django.conf.urls". That > takes about ten minutes, if you count the time to locate the information in > the release notes and make the commit. It's not really, though is it? You encounter the problem because you've upgraded django version; this will not be the only thing that is broken, and so fixing this one thing will not enable you to run your test suites.. it can take several iterations before you know that it is fixed. If you track django development and have used django for several years, then these changes are relatively easy. If you are new to using django, it is not so obvious and easy; as an example, we had an old site running on django 1.3 that we wanted to move to 1.4 so that we are using the same version of django throughout; this story was scored at 8 points, it took a junior developer much longer than 8 points and wasn't finished in a single sprint - and 1.3->1.4 was *easy*! We prefer to spend our points on our own features (and senior developers are expensive :) Cheers Tom -- 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/CAFHbX1%2BW2E0UO4kZZBwGHf%3DbA4%2BH4-u95T3jtGkUVX03ZOzQuQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
