Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#23015 closed Bug (fixed)

Don't announce Django 2.0 as a backwards-incompatible release

Reported by: Aymeric Augustin Owned by: Tim Graham
Component: Documentation Version: dev
Severity: Normal Keywords:
Cc: 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

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.

Change History (9)

comment:1 by Aymeric Augustin, 10 years ago

Related: docs/internals/howto-release-django.txt and docs/releases/1.1.2.txt uses "major release" to refer to what is defined by docs/internals/release-process.txt as a "minor release".

comment:2 by Aymeric Augustin, 10 years ago

We should redefine "major release" in docs/internals/release-process.txt. Everyone considers Django 1.x, 1.y, etc. major releases.

comment:3 by Tim Graham, 10 years ago

Owner: changed from nobody to Tim Graham
Status: newassigned
Triage Stage: UnreviewedAccepted

comment:4 by Tim Graham, 10 years ago

Has patch: set

comment:5 by jarshwah, 10 years ago

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)?

comment:6 by Tim Graham, 10 years ago

Current consensus is that no such changes will occur in the foreseeable future. If such changes are needed at some point, then we'll cross that bridge when the time comes.

comment:7 by Aymeric Augustin, 10 years ago

Triage Stage: AcceptedReady for checkin

Looks good, thank you!

comment:8 by Tim Graham <timograham@…>, 10 years ago

Resolution: fixed
Status: assignedclosed

In dd6ef3197a4d10696c5ef4ddb55b0d4baaba4340:

Fixed #23015 -- Fixed major/minor release terminology in docs.

comment:9 by Tim Graham <timograham@…>, 10 years ago

In dcb1b971c254c4c23216b8335ec40abb7d30b288:

[1.7.x] Fixed #23015 -- Fixed major/minor release terminology in docs.

Backport of dd6ef3197a from master

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