Hello Bernhard, In my experience, Django strikes a good balance between adding new features without moving so quickly that it's impossible to keep up. That being said, third-party packages *can* vary widely in the speed with which they add support for new Django versions after a new major release.
What are some changes in Django over the past few releases that you felt were too significant or costly to address? Tobias On Tue, Apr 4, 2017 at 3:15 PM, Bernhard Posselt <nukeawh...@gmail.com> wrote: > Hi guys :) > > I'm maintaining a Django project that uses 6 apps: > > * djangorestframework, > > * django-parler (database translations), > > * django-allauth (openid & richer account settings) > > * django-recaptcha2 (simple recaptcha widget) > > * django-csp > > * django-cors-middleware > > Each time a new Django version is published it takes me at least a few > weeks to upgrade. The reason is that each release breaks something in > the apps that I use. Code that I wrote myself can usually be fixed > pretty quickly. > > Personally I don't think that the number of dependencies is excessive. > Furthermore I think that Django developers want to offload as much > functionality as possible to thirdparty apps to improve maintainability > so I doubt that I'm the only one with these issues. > > I know that deprecating and cleaning up things is *very* important to > keep the framework alive however was it ever considered to tune down the > frequency of breaking changes (like only remove features in a new LTS > release)? > > Apart from that would it be possible to adopt semver? If you had > followed semver closely, each 1.x release would have actually been a > major release (e.g. 1.1 -> 2.0.0, 1.2 -> 3.0.0) and your point releases > would need to contain three version numbers (e.g. 1.11.0 and not 1.11). > > I know that this versioning approach leads to very high version number > in a short amount of time but that's essentially what Django does: > breaking compat with each release :) > > > > -- > 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 https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://groups.google.com/d/ms > gid/django-developers/7fde82bd-352d-9946-2cbc-699f04bd8773%40gmail.com. > For more options, visit https://groups.google.com/d/optout. > -- *Tobias McNulty*Chief Executive Officer tob...@caktusgroup.com www.caktusgroup.com -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMGFDKRDPBk9CSMe%3DOE-xN1zBTkya6rxWzabvnEQWPe4-GhOBA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
