kubernetes / committee-security-response

Kubernetes Security Process and Security Committee docs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Update `security-release-process.md` with ref to security-release-team@ email

lukehinds opened this issue · comments

Previously release-managers-private@ was nested within security@.

As of kubernetes/sig-release#900, there will be a separate security-release-team@ email address.

The security/security-release-process.md document should outline the new security-release-team@ email address and how this address should be used when wanting to bring the security release team into a discussion and allow release coordination of a security fix.

Corresponding releng tracking issue: kubernetes/sig-release#896

/assign

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/remove-lifecycle rotten
/lifecycle frozen
/reopen

This needs some input from @kubernetes/product-security-committee.
It's the last item for kubernetes/sig-release#896.

@justaugustus: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/lifecycle frozen
/reopen

This needs some input from @kubernetes/product-security-committee.
It's the last item for kubernetes/sig-release#896.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

This needs some input from @kubernetes/product-security-committee.

Hey @kubernetes/product-security-committee 👋, do you think you can provide the required information how to move forward with this topic?

/assign

@lukehinds thank you for picking this up! Can we provide anything from the SIG release perspective to support you?

Hey @lukehinds, may I ask you about an update on this?

Hey @lukehinds, may I ask you about an update on this?

#129

Tim is reviewing #129, so:
/unassign @justaugustus @saschagrunert