From 4aa2cd6f68cd06ddbbb227d2f63efc2bd51054ca Mon Sep 17 00:00:00 2001
From: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com>
Date: Tue, 28 Jan 2025 16:09:14 +0100
Subject: [PATCH] [5.2.x] Clarified the Releaser's discretion for determining
 and postponing the release date.

Backport of 8a6b4175d790424312965ec77e4e9b072fba188b from main.
---
 docs/internals/howto-release-django.txt | 8 ++++++--
 1 file 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.