One approach worth consideration is dropping deprecated features only after next LTS. This would mean that any non-deprecated feature that is available in current LTS will also be available (but possibly deprecated) in the next LTS. This should make a development model where code is developed using latest stable release, and supported using latest LTS a lot easier.
I don't belileve we can offer an official LTS-to-LTS upgrade guide (maintaining one is simply too much work). You can of course try to do that, but you'll likely get a better result by upgrading one point release at a time. - Anssi On Thu, May 7, 2015 at 11:04 AM, Abdullah Esmail <abdullah.esm...@gmail.com> wrote: > Hello, > I apologize if this has been discussed already. I searched the topics, but > didn't find anything. > First, I'd like to thank all of you for the truly amazing framework. I've > been using django since 1.0 and it made my life much more easier and > enjoyable and _stable_. > > The reason why I love django is that stability is a high priority, > backward-compatibility is well maintained and clear, crystal-clear and > extra-detailed documentation, the "batteries-included" aspect, based on > python, and the steady and stable evolution of the framework. Everything is > well put together in an almost-perfect package. Thank you. > > To my main issue, have you explored the possibility of creating a direct > path from one LTS release to the next? > I think the "official" way of doing this now is to go through all releases > in-between (1.4 -> 1.5 -> 1.6 -> 1.7 -> 1.8). > It would be really great if there was a direct LTS-to-LTS path (1.4 -> 1.8). > > I'm not sure if the new system check framework can play a role here to make > this easier than before. > This might add a whole new layer of complexity and extra work, but I believe > it's worth it. > If it makes any difference, I don't mind helping with this and actually > bringing this feature to life. > I'm not that familiar with the internals of django, but I'm willing to learn > and get my hands dirty. > > I guess I should ask, is there a good reason why there is no direct upgrade > path between LTS releases? > Do you guys think it's not worth the extra effort and the current way is an > acceptable trade-off? > > Thank you, > > -- > 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/96e73e82-93fe-4ef7-92c4-ba67abb35b37%40googlegroups.com. > 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/CALMtK1E-F8i4_%2BYLH6KRzWMvuJEmr8geDDU9mUY9MFRudhLw0Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
