#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
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"dd6ef3197a4d10696c5ef4ddb55b0d4baaba4340"]:
{{{
#!CommitTicketReference repository=""
revision="dd6ef3197a4d10696c5ef4ddb55b0d4baaba4340"
Fixed #23015 -- Fixed major/minor release terminology in docs.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23015#comment:8>
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.7368d48cba617901d21b3bc3309b5cc6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
