From 347ed932129504e71a53a8bd2f7fd72ce1480d9b Mon Sep 17 00:00:00 2001 From: Brandon Philips Date: Sun, 29 Jan 2017 10:13:15 -0800 Subject: security-release-process: add release managers The release managers should be on the list as they are going to be the central point of coordination for testing, release, and communication. --- contributors/devel/security-release-process.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/contributors/devel/security-release-process.md b/contributors/devel/security-release-process.md index aa3fdd12..6d62873f 100644 --- a/contributors/devel/security-release-process.md +++ b/contributors/devel/security-release-process.md @@ -17,6 +17,12 @@ The initial Product Security Team will consist of five volunteers who are all su - We haven't specified a way to cycle the Product Security Team; but we need this process deployed quickly as our current process isn't working. I (@philips) will put a deadline of March 1st 2017 to sort that. +## Release Manager Role + +ALso included on the private [Kubernetes Security](https://groups.google.com/forum/#!forum/kubernetes-security) list are all [Release Managers](https://github.com/kubernetes/community/wiki). + +It is the responsbility of the Product Security Team to add new Release Managers and remove Release Managers as Kubernetes minor releases are deprecated. + ## Disclosures ### Private Disclosure Processes -- cgit v1.2.3