diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-04-05 11:15:20 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-04-05 11:15:20 -0700 |
| commit | e5c8b899e08efb110829c32910a696ee1983e451 (patch) | |
| tree | 5403dbe254aa7c4f3e68115eb8fb2f94326c25af | |
| parent | 50d65c462c5b3cad25bb20671767737fed6c410b (diff) | |
| parent | ae9c1bfdaf2f8ef9da8901ba3f6657ca13fee2bf (diff) | |
Merge pull request #3515 from tpepper/master
devel guide: update patch release team contact for cherry picks
| -rw-r--r-- | contributors/devel/sig-release/cherry-picks.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/contributors/devel/sig-release/cherry-picks.md b/contributors/devel/sig-release/cherry-picks.md index 097fef85..934111a3 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 |