diff options
| author | Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> | 2025-01-28 16:09:14 +0100 |
|---|---|---|
| committer | Sarah Boyce <42296566+sarahboyce@users.noreply.github.com> | 2025-01-28 18:20:30 +0100 |
| commit | 9d1945df8fe8bec6cec8d6e4c69216655262d985 (patch) | |
| tree | a6f537e94c45c99eb6ca646e99b0aa170f16cbe2 | |
| parent | 3c1f94d70f23c10f5b05509136d1ecdc62110ddb (diff) | |
[5.1.x] Clarified the Releaser's discretion for determining and postponing the release date.
Backport of 8a6b4175d790424312965ec77e4e9b072fba188b from main.
| -rw-r--r-- | docs/internals/howto-release-django.txt | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index bedb1b8822..2186a489e4 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -185,8 +185,12 @@ A week before a security release A few days before any release ----------------------------- -#. As the release approaches, watch Trac to make sure no release blockers - are left for the upcoming release. +#. As the release approaches, watch Trac to make sure no release blockers are + left for the upcoming release. Under exceptional circumstances, such as to + meet a pre-determined security release date, a release could still go ahead + with an open release blocker. The releaser is trusted with the decision to + release with an open release blocker or to postpone the release date of a + non-security release if required. #. Check with the other mergers to make sure they don't have any uncommitted changes for the release. |