#23015: Don't announce Django 2.0 as a backwards-incompatible release
-------------------------------+------------------------------------
Reporter: aaugustin | Owner: timo
Type: Bug | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by smeatonj):
I think the idea here is good. But what happens in the future if some
serious backward-incompatible changes need to land - there would be no way
to indicate with version numbers that big shift. Or, is the idea that no
such serious changes will ever occur all at once (similar to now, where
there's 2 major releases to slowly deprecate functionality)?
--
Ticket URL: <https://code.djangoproject.com/ticket/23015#comment:5>
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/067.87c8611a7ea5a9e351bd5cf31ad069eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
