Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to security-release-team@ #129

Closed
wants to merge 5 commits into from
Closed

Update to security-release-team@ #129

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
fb0345e
Update to security-release-team@
Sep 7, 2021
4ec334b
Update security-release-process.md
lukehinds Jan 31, 2022
220c1dd
Update security-release-process.md
lukehinds Jan 31, 2022
b7abf3e
Update security-release-process.md
lukehinds Jan 31, 2022
d9fb172
Update security-release-process.md
lukehinds Feb 7, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions security-release-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,17 +123,17 @@ Their rotation will involve the following:

#### SIG Release Roles

Included on the [private Release Managers list](https://groups.google.com/a/kubernetes.io/forum/#!forum/release-managers-private)
Included on the [private Release Managers list](https://groups.google.com/a/kubernetes.io/forum/#!forum/security-release-team)
are the following members:

- [Release Managers](https://git.k8s.io/sig-release/release-managers.md#release-managers)
- [Release Managers](https://git.k8s.io/website/content/en/releases/release-managers.md)
lukehinds marked this conversation as resolved.
Show resolved Hide resolved
(manage build and release aspects when a security fix must be delivered)
- [SIG Release Chairs](https://git.k8s.io/sig-release/release-managers.md#sig-release-chairs)
- [SIG Release Chairs](https://git.k8s.io/website/content/en/releases/release-managers.md#chairs)
lukehinds marked this conversation as resolved.
Show resolved Hide resolved

It is the responsibility of the [SIG Release Chairs](https://git.k8s.io/sig-release/release-managers.md#sig-release-chairs)
lukehinds marked this conversation as resolved.
Show resolved Hide resolved
to curate and maintain the various release role access controls across release cycles.

The [Build Admins](https://git.k8s.io/sig-release/release-managers.md#build-admins)
The [Build Admins](https://git.k8s.io/website/content/en/releases/release-managers.md#build-admins)
lukehinds marked this conversation as resolved.
Show resolved Hide resolved
(Googlers with access to build/publish Kubernetes deb/rpm packages) are not
lukehinds marked this conversation as resolved.
Show resolved Hide resolved
explicitly part of the private security release team, but are also involved in
delivery and must abide by the private disclosure process.
Expand Down