psc/releng: Update references to the security release process #900
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
do-not-merge/hold
k8s-ci-robot
added
area/release-team
k8s-ci-robot
added
size/M
3 tasks
k8s-ci-robot
added
the
lgtm
|
/hold For more eyes. |
justaugustus
force-pushed
the
security
branch
from
088a085 to
5601f6e
Compare
k8s-ci-robot
added
size/L
|
Ready for review... For PSC approval: For RT Leads visibility: |
18 tasks
|
To look over RT Lead changes: |
liggitt
reviewed
Dec 9, 2019
| @@ -381,6 +382,17 @@ However, there is an embargo policy which requires the nomock release publicatio | |||
|
|
|||
| To better prepare and see what to expect, this is a sequence of events that took place on past [official release days](https://docs.google.com/document/d/1K0B91lgeEiJTbT602VloA5arb6AkaTif-MLryaHmlYc/edit?usp=sharing). | |||
|
|
|||
| #### Security fixes | |||
|
|
|||
| The Product Security Committee (PSC) may contact you if there are security fixes needed on the release branch. | |||
There was a problem hiding this comment.
suggest adding the method of communication to expect?
Suggested change
| The Product Security Committee (PSC) may contact you if there are security fixes needed on the release branch. | |
| The Product Security Committee (PSC) may contact you via $mailing-list if there are security fixes needed on the release branch. |
- Include security-release-team@ as a contact in release-managers.md The Product Security Committee and Release Managers will now coordinate security releases using this list. - Ensure Branch Manager membership on release-managers-private is documented and included in the Release Manager onboarding template - Mention the Security Release Process in the Branch Manager handbook - Update table of contents in Patch Release Team handbook Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Security release coordination now happens between the Product Security Committee, Patch Release Team, Branch Managers, and SIG Chairs. Information regarding security releases will be disseminated to Release Team Leads by Branch Managers on a need-to-know basis. Signed-off-by: Stephen Augustus <[email protected]>
Here we add an onboarding template for Release Team Leads and Lead Shadows and move information about requisite access from the handbook and into the issue template. Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
justaugustus
force-pushed
the
security
branch
from
e1cab27 to
4b7fe58
Compare
|
PSC bits lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, justaugustus, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Releasing the hold as we have PSC and Releng approval. /hold cancel |
k8s-ci-robot
removed
the
do-not-merge/hold
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
psc/releng: Update references to the security release process
Include security-release-team@ as a contact in release-managers.md
The Product Security Committee and Release Managers will now
coordinate security releases using this list.
Ensure Branch Manager membership on release-managers-private is
documented and included in the Release Manager onboarding template
Mention the Security Release Process in the Branch Manager handbook
Update table of contents in Patch Release Team handbook
lint: Fix markdown warnings in Release Team Lead handbook
release-team-lead: Remove reference to the private Release Managers list
Security release coordination now happens between the Product Security
Committee, Patch Release Team, Branch Managers, and SIG Chairs.
Information regarding security releases will be disseminated to Release
Team Leads by Branch Managers on a need-to-know basis.
release-team-lead: Add onboarding template
Here we add an onboarding template for Release Team Leads and Lead
Shadows and move information about requisite access from the handbook
and into the issue template.
Signed-off-by: Stephen Augustus [email protected]
/hold
(there are few things I want to tweak on the RT Lead handbook before merge)cc: @kubernetes/product-security-committee @kubernetes/release-engineering @kubernetes/release-team
ref: #896
/area release-eng release-team
/committee product-security
/milestone v1.17
/kind documentation cleanup
/priority important-soon