Merge pull request #28810 from Shubham82/Link-Embargo-Policy
Mention Security Embargo Policy.
This commit is contained in:
@@ -10,6 +10,7 @@ and building/packaging Kubernetes.
|
||||
The responsibilities of each role are described below.
|
||||
|
||||
- [Contact](#contact)
|
||||
- [Security Embargo Policy](#security-embargo-policy)
|
||||
- [Handbooks](#handbooks)
|
||||
- [Release Managers](#release-managers)
|
||||
- [Becoming a Release Manager](#becoming-a-release-manager)
|
||||
@@ -28,6 +29,10 @@ The responsibilities of each role are described below.
|
||||
| [release-managers-private@kubernetes.io](mailto:release-managers-private@kubernetes.io) | N/A | Private | Private discussion for privileged Release Managers | Release Managers, SIG Release leadership |
|
||||
| [security-release-team@kubernetes.io](mailto:security-release-team@kubernetes.io) | [#security-release-team](https://kubernetes.slack.com/archives/G0162T1RYHG) (channel) / @security-rel-team (user group) | Private | Security release coordination with the Product Security Committee | [security-discuss-private@kubernetes.io](mailto:security-discuss-private@kubernetes.io), [release-managers-private@kubernetes.io](mailto:release-managers-private@kubernetes.io) |
|
||||
|
||||
### Security Embargo Policy
|
||||
|
||||
Some information about releases is subject to embargo and we have defined policy about how those embargos are set. Please refer [Security Embargo Policy](https://github.com/kubernetes/security/blob/master/private-distributors-list.md#embargo-policy) here for more information.
|
||||
|
||||
## Handbooks
|
||||
|
||||
**NOTE: The Patch Release Team and Branch Manager handbooks will be de-duplicated at a later date.**
|
||||
|
||||
Reference in New Issue
Block a user