Don't announce Django 2.0 as a backwards-incompatible release
|Reported by:||aaugustin||Owned by:||timo|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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:3 Changed 2 years ago by timo
- Owner changed from nobody to timo
- Status changed from new to assigned
- Triage Stage changed from Unreviewed to Accepted
comment:8 Changed 2 years ago by Tim Graham <timograham@…>
- Resolution set to fixed
- Status changed from assigned to closed