From ae9c1bfdaf2f8ef9da8901ba3f6657ca13fee2bf Mon Sep 17 00:00:00 2001 From: Tim Pepper Date: Mon, 25 Mar 2019 16:17:52 -0700 Subject: [PATCH] update patch release team contact for cherry picks We're adding a GitHub team for the patch managers and have a group mail alias to make it easier contacting the folks who shepherd cherry picks across the arc of time, documented in the release repo. Signed-off-by: Tim Pepper --- contributors/devel/sig-release/cherry-picks.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/contributors/devel/sig-release/cherry-picks.md b/contributors/devel/sig-release/cherry-picks.md index 097fef857..934111a35 100644 --- a/contributors/devel/sig-release/cherry-picks.md +++ b/contributors/devel/sig-release/cherry-picks.md @@ -40,9 +40,11 @@ branches. * Milestones on cherry-pick PRs should be the milestone for the target release branch (for example, milestone 1.11 for a cherry-pick onto release-1.11). - * You can find the current release team members in the - [appropriate release folder](https://git.k8s.io/sig-release/releases) for the target release. - You may cc them with `<@githubusername>` on your cherry-pick PR. + * During code freeze, to get attention on a cherry-pick by the current + release team members see the [appropriate release folder](https://git.k8s.io/sig-release/releases) + for the target release's team contact information. You may cc them with + `<@githubusername>` on your cherry-pick PR. + * For prior branches, check the [patch release schedule](https://git.k8s.io/sig-release/releases/patch-releases.md), which includes contact information for the patch release team. ## Cherry-pick Review