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 17:18:08 +0000 |
| commit | 8a6b4175d790424312965ec77e4e9b072fba188b (patch) | |
| tree | 2dfda5d5fbfe71161d0891edf2dedeb081f735c5 | |
| parent | efec74b90868c2e611f863bf4301d92ce08067e8 (diff) | |
Clarified the Releaser's discretion for determining and postponing the release date.
| -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 b8a524cc84..b1fb435c48 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -188,8 +188,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. |