Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarified backport policy for regressions. #12319

Merged
merged 1 commit into from Jan 15, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/internals/release-process.txt
Expand Up @@ -141,7 +141,8 @@ page for the current state of support for each version.

* Major functionality bugs in new features of the latest stable release.

* Regressions from older versions of Django.
* Regressions from older versions of Django introduced in the current release
series.

The rule of thumb is that fixes will be backported to the last feature
release for bugs that would have prevented a release in the first place
Expand Down