kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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 <tpepper@vmware.com>
This commit is contained in:
Tim Pepper 2019-03-25 16:17:52 -07:00
parent e7b8b9752a
commit ae9c1bfdaf
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
contributors/devel/sig-release/cherry-picks.md
View File

@ -40,9 +40,11 @@ branches.
* Milestones on cherry-pick PRs should be the milestone for the target * 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 branch (for example, milestone 1.11 for a cherry-pick onto
release-1.11). release-1.11).
* You can find the current release team members in the * During code freeze, to get attention on a cherry-pick by the current
[appropriate release folder](https://git.k8s.io/sig-release/releases) for the target release. release team members see the [appropriate release folder](https://git.k8s.io/sig-release/releases)
You may cc them with `<@githubusername>` on your cherry-pick PR. 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 ## Cherry-pick Review