Opened 7 years ago

Closed 7 years ago

#28579 closed Cleanup/optimization (fixed)

Clarify 2.0 is just a new version numbering scheme

Reported by: Collin Anderson Owned by: nobody
Component: Documentation Version: dev
Severity: Normal Keywords:
Cc: Collin Anderson Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I've seen a question or two asking how big of a break will 2.0 be.

It could be worth clarifying near the top of the release notes that 2.0 is part of a new version numbering scheme, and there is no major / unprecedented backwards compatibility. It's no bigger of a change than from 1.8 -> 1.9 besides dropping 2.x support.

Change History (5)

comment:1 by Collin Anderson, 7 years ago

Cc: Collin Anderson added

comment:2 by Collin Anderson, 7 years ago

Needs documentation: set

comment:3 by Tim Graham, 7 years ago

Has patch: set
Needs documentation: unset
Triage Stage: UnreviewedAccepted

comment:4 by Collin Anderson, 7 years ago

Triage Stage: AcceptedReady for checkin

comment:5 by GitHub <noreply@…>, 7 years ago

Resolution: fixed
Status: newclosed

In 4844af90:

Fixed #28579 -- Doc'd upgrade effort expectations for Django 2.0.

Note: See TracTickets for help on using tickets.
Back to Top