#23015: Don't announce Django 2.0 as a backwards-incompatible release
-----------------------------------------+------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
Over the last years, the consensus has slowly shitfed toward making the
1.9 -> 2.0 transition not more disruptive than other 1.x -> 1.y
transitions (where y = x + 1).
The first section of https://docs.djangoproject.com/en/dev/internals
/release-process/ should be update to reflect this.
--
Ticket URL: <https://code.djangoproject.com/ticket/23015>
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/052.61bcc5e0bb619e9db766f8948ac81dc0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
