Commit 0966a168d6c for woocommerce

commit 0966a168d6cbd11a86f8b005bb1fc83a470d23eb
Author: Rafael Meneses <meneses.tio@gmail.com>
Date:   Fri Oct 9 19:32:57 2026 -0300

    Set a 24-hour minimum on staging before the stable go/no-go (#69562)

    docs(releases): Set a 24-hour minimum on staging before the stable go/no-go

    The go/no-go waits for RC staging to finish, but nothing says how long
    that is. The only number is the 4-hour watch, so on paper the RC and
    stable could ship the same day.

    Keep the RC on staging for at least 24 hours before the go/no-go. The
    release lead can wait longer.

    Refs ARC-1843

    Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

diff --git a/docs/contribution/releases/readiness.md b/docs/contribution/releases/readiness.md
index 5cc1cd4f05c..2145bbe9c34 100644
--- a/docs/contribution/releases/readiness.md
+++ b/docs/contribution/releases/readiness.md
@@ -36,6 +36,8 @@ The checklist covers four areas:

 A deliberate decision to ship, made while there is still time to not ship. It runs once the RC has finished its staging monitoring - holding it earlier would mean deciding before the RC has been seen on real sites. The release lead and the Product DRI confirm the readiness verdicts still hold, review the RC's sweep and staging thread, and note any fix merged after the RC and whether it ran on staging. Then they record the decision as a comment on the release sub-issue on GitHub: **go**, **no-go**, or **go with conditions** - with names.

+The RC stays on staging for at least 24 hours before the go/no-go. The release lead can wait longer, for example when a finding is still open or a fix merged after the RC hasn't run on staging.
+
 Recorded decisions are the input for release retrospectives and future updates to these checklists.

 ## For point releases
diff --git a/docs/contribution/releases/schedule.md b/docs/contribution/releases/schedule.md
index 5d11d96ee64..d7140c5211c 100644
--- a/docs/contribution/releases/schedule.md
+++ b/docs/contribution/releases/schedule.md
@@ -54,6 +54,7 @@ If anything is found at this stage, a fix is merged into the release branch (`re
 ### Final Release (+1 day)

 We make the stable release version available to everyone.
+The stable build waits until the RC has been on staging for at least 24 hours.
 At this point, the Developer Advocacy team publishes release highlights that are prepared in advance ([example](https://developer.woocommerce.com/2025/06/09/woocommerce-9-9-its-fast-period/)).

 ### Point/Patch Releases