From b4275ba7b2e957d53e119ff2a847dede39333cee Mon Sep 17 00:00:00 2001 From: Luke Heath Date: Tue, 28 Oct 2025 15:58:28 -0500 Subject: [PATCH] Add guidelines for discussing release dates (#34892) --- handbook/engineering/README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index 9a9ed1fef5..60c1db9327 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -270,6 +270,11 @@ The [Fleet releases Google calendar](https://calendar.google.com/calendar/embed? When target release dates are changed on the calendar, the release ritual DRI also updates the milestone due date. +### Discuss release dates + +A single Slack thread is created in the #help-releases channel for every release candidate. Any discussions about release dates should be kept within the release candidate's thread. + + ### Handle process exceptions for non-released code Some of our code does not go through a scheduled release process and is released immediately via GitHub workflows: