Commit 6a0e1bbba1f for woocommerce

commit 6a0e1bbba1fcfad4dc900fc9ce6607eccee0ea2e
Author: Rafael Meneses <meneses.tio@gmail.com>
Date:   Thu Jul 23 12:08:34 2026 -0300

    Make the Product DRI confirmation step executable in the release kickoff template (#66896)

    docs(release): make the Product DRI confirmation step executable

    The kickoff template told the release lead to "confirm the Product DRI"
    without saying how or with whom - a first-time release lead had no
    defined move (raised on #66805 post-merge).

    Point the step at @woo-core-release in #woo-core-releases: the group
    confirms the product-side owner for the cycle and the lead records the
    name on the tracking issue. Same mechanism documented in the release
    roles section of the readiness page.

    Resolving the DRI automatically at kickoff, like the release lead
    rotation, stays a separate follow-up.

    Refs ARC-1860

    Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

diff --git a/.linear/release-kickoff.md b/.linear/release-kickoff.md
index 54d5b058280..34196a30893 100644
--- a/.linear/release-kickoff.md
+++ b/.linear/release-kickoff.md
@@ -19,7 +19,7 @@ This issue provides visibility on the progress of the release process of WooComm
 ⚠ Dear release lead:

 - Please read this issue carefully and familiarize yourself with the [release process documentation](https://developer.woocommerce.com/docs/contribution/releases/).
-- Confirm the Product DRI for this cycle and edit the line above with their name. The readiness review (RC sub-issue) and the go/no-go (stable sub-issue) need both of you.
+- Confirm the Product DRI for this cycle: ask `@woo-core-release` in `#woo-core-releases` to confirm the product-side owner for this release, then edit the line above with their name. The readiness review (RC sub-issue) and the go/no-go (stable sub-issue) need both of you.
 - Join the release channels in Slack (`#woo-core-releases`, `#woo-core-releases-notifications`), where discussions happen and notifications are sent.
 - For every release in the cycle, there's a corresponding sub-issue. On the date of each release (see schedule above), open the relevant issue and follow the instructions in it.
 - Any additional point/patch releases after the first stable must be tracked as well. Run the **[Release: Create Tracking Issue]({repository_url}/actions/workflows/release-create-tracking-issue.yml)** workflow with the version (e.g., `{release_main_version}.1`) to create the sub-issue.
diff --git a/docs/contribution/releases/readiness.md b/docs/contribution/releases/readiness.md
index 36cc4b30bee..7d6d8e39f29 100644
--- a/docs/contribution/releases/readiness.md
+++ b/docs/contribution/releases/readiness.md
@@ -15,7 +15,7 @@ Each cycle has two named owners, listed on the parent tracking issue:
 * **Release lead** (engineering) - runs the release process end to end: builds, publishes, monitors, and executes the run-books.
 * **Product DRI** - the product-side counterpart. Joins the readiness review at RC and the go/no-go before stable, and owns the product read on open findings: what blocks the release, what waits for a point release, and what ships with a known-issues note.

-The release lead is assigned by rotation via the [Release: Assignment workflow](/docs/contribution/releases/workflows). The Product DRI is confirmed per cycle on the tracking issue.
+The release lead is assigned by rotation via the [Release: Assignment workflow](/docs/contribution/releases/workflows). The Product DRI is confirmed per cycle on the tracking issue: the release lead asks `@woo-core-release` in `#woo-core-releases`, and the group confirms the product-side owner for the release.

 ## Readiness review (at RC)