Commit 7102bd58685 for woocommerce

commit 7102bd58685dbb66e9af11c039277ac1036e7d25
Author: Rafael Meneses <meneses.tio@gmail.com>
Date:   Thu Oct 15 19:30:58 2026 -0300

    Add the 24-hour RC staging minimum to the release checklist (#69880)

    * Add the RC staging minimum to the release checklist

    * Shorten the RC staging checklist wording

diff --git a/.linear/release-kickoff-patch.md b/.linear/release-kickoff-patch.md
index c60d1233ab8..6cf84a82b3b 100644
--- a/.linear/release-kickoff-patch.md
+++ b/.linear/release-kickoff-patch.md
@@ -14,6 +14,7 @@ Keep the _[Release Troubleshooting & Recovery](https://developer.woocommerce.com

 For scheduled stable releases, hold this after the RC has finished its staging monitoring and before starting the build below, with the Product DRIs named on the parent tracking issue - ping `@woo-core-release` in Slack if you need to reach them or aren't sure who's available. Bring in QualityOps and the Atomic contact when staging or monitoring left open questions. See the [readiness guide](https://developer.woocommerce.com/docs/contribution/releases/readiness/) for details.

+- [ ] **RC staging time** (scheduled stable releases only). Confirm the RC has been on staging for at least 24 hours before go/no-go. The release lead can wait longer.
 - [ ] **Readiness still holds.** For a scheduled release, re-read the readiness comments on the RC sub-issue and record what changed since: new findings with their verdicts, and fixes merged into the release branch after the RC, noting whether each ran on staging. For a point release, run the readiness criteria as described below.
 - [ ] **RC evidence** (scheduled releases). Open the QIT sweep for the RC and the staging thread from step 5 of the RC sub-issue. Record both links and a verdict for anything new.
 - [ ] **Decision.** Comment on this GitHub issue: **go**, **no-go**, or **go with conditions** (list them), with the names behind it. A new comment thread started on the Linear mirror does not sync back here.