Re: Django versioning and breaking changes policy

I think people are always going to run into such kind of issues until they decide to add django-master to their test matrix​, so that each dependency and project should always have the chance to be ready for the next version of Django "0day". But perhaps I'm missing something. Best James -- You

Re: Django versioning and breaking changes policy

Django doesn't transition to semver. It keeps its own versioning scheme but reuses some good ideas from semver. -- Aymeric. > On 5 Apr 2017, at 00:29, Bernhard Posselt wrote: > > Oh wow, haven't seen that yet, thank you :) > > Just make sure to follow the semver spec closely if you transit

Re: Django versioning and breaking changes policy

See? This is exactly what I told you you could expect ... to be shown the new release process details :) [For those playing at home, Bernhard raised this concern on IRC first, and I recommended bringing it here. He expressed concern about being roasted, and I predicted someone would introduce

Re: Django versioning and breaking changes policy

Oh wow, haven't seen that yet, thank you :) Just make sure to follow the semver spec closely if you transition to semver, because it can cause issues for parsers. Also the spec is more restrictive than you'd think with regards to syntax (source: working with semver in my current Django project)

Re: Django versioning and breaking changes policy

Hi Tobias, my impression is that as a developer you can keep up with the changes pretty well and I don't think it's related to features being too costly to address. The main issue is really third-party code. The only thing that I can currently think of as a comparison is the Angular 1.x branch: I

Re: Django versioning and breaking changes policy

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.

Re: Django versioning and breaking changes policy

Hello, As far as I can tell, recent modifications to the release process means it will meet your expectations going forwards. Take a look at https://docs.djangoproject.com/en/dev/internals/release-process/ for details. Best reg

Django versioning and breaking changes policy

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 versio