Update security-release-process.md to clarify when to close the github tracking issue.

kubernetes / committee-security-response

Kubernetes Security Process and Security Committee docs

Apache License 2.0

161 stars 66 forks source link

Update security-release-process.md to clarify when to close the github tracking issue. #191

Closed cji closed 4 months ago

cji commented 7 months ago

We should add a step on when to close out the public github tracking issue. I propose that once we've sent everything out, fixes are released, and we've sent the CVE data to MITRE, we can consider the issue "closed" as our process is completed.

k8s-ci-robot commented 7 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cji

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: - ~~[OWNERS](https://github.com/kubernetes/committee-security-response/blob/main/OWNERS)~~ [cji] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

Mark this PR as fresh with /remove-lifecycle stale
Close this PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

ritazh commented 4 months ago

@cji can you please rebase so we can get it merged

cji commented 4 months ago

@ritazh done!

ritazh commented 4 months ago

/lgtm