#23469: django_1_6_0 compatibility check yields false posititves
--------------------------------------+------------------------------------
Reporter: brutasse | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (System checks) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by carljm):
We haven't made any changes to our deprecation process to account for LTS,
so I don't think we can really support skipping from LTS to LTS; you'd
miss entire deprecations without ever seeing any warnings. So I think when
the next LTS comes out, we just need to be very clear in its release notes
that upgrading direct from LTS to LTS is not supported, you need to go
major version by major version.
I don't think there's any urgency about removing old upgrade checks in
general, if they don't have false positives, but I'm definitely in favor
of removing this particular problematic check from master (and maybe even
1.7.X) at this point.
--
Ticket URL: <https://code.djangoproject.com/ticket/23469#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.8e8ad45b1e2775419b0586aa32c93d17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
