#23015: Don't announce Django 2.0 as a backwards-incompatible release
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: timo
Type: Bug | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
Has patch: 1 | checkin
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"dcb1b971c254c4c23216b8335ec40abb7d30b288"]:
{{{
#!CommitTicketReference repository=""
revision="dcb1b971c254c4c23216b8335ec40abb7d30b288"
[1.7.x] Fixed #23015 -- Fixed major/minor release terminology in docs.
Backport of dd6ef3197a from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23015#comment:9>
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.fcb4446ba1e61f8f4be6587994088827%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
