Improve Process Documentation for Embargoed Releases

Question

Improve Process Documentation for Embargoed Releases

tallclair opened this issue 5 years ago · comments

Tim Allclair commented 5 years ago

Including:

decision flow documentation around when/whether to do branch freezes and CVE-only patch releases, versus keeping the train moving on a consistent schedule
how non-k/k projects should handle embargoed releases
who owns each step in the embargoed release process

Tim Allclair commented 5 years ago

/help

Kubernetes Prow Robot · Answer 1 · Fri Nov 15 2019 05:32:36 GMT+0800 (China Standard Time)

@tallclair:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

fejta-bot · Answer 2 · Thu Feb 13 2020 06:00:35 GMT+0800 (China Standard Time)

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

Tim Allclair · Answer 3 · Wed Feb 19 2020 09:18:02 GMT+0800 (China Standard Time)

/remove-lifecycle stale

fejta-bot · Answer 4 · Tue May 19 2020 09:33:25 GMT+0800 (China Standard Time)

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

Tim Allclair · Answer 5 · Thu May 21 2020 08:24:06 GMT+0800 (China Standard Time)

Partially captured by https://github.com/kubernetes/security/blob/master/psc-oncall.md#incident-response-workflow

We could use better documentation for the private release process though.

/remove-lifecycle stale

fejta-bot · Answer 6 · Wed Aug 19 2020 09:23:13 GMT+0800 (China Standard Time)

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

fejta-bot · Answer 7 · Fri Sep 18 2020 10:05:45 GMT+0800 (China Standard Time)

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

fejta-bot · Answer 8 · Sun Oct 18 2020 10:48:43 GMT+0800 (China Standard Time)

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

Kubernetes Prow Robot · Answer 9 · Sun Oct 18 2020 10:48:55 GMT+0800 (China Standard Time)

@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.