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

Jump to bottom

Break Release Notes Down By Sig #348

Closed
grodrigues3 opened this issue Jun 15, 2017 · 7 comments
Closed

Break Release Notes Down By Sig #348

grodrigues3 opened this issue Jun 15, 2017 · 7 comments
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@grodrigues3
Copy link

The release team's goal was to achieve better visibility into the 1.7 release by:

Enforcing that all issues in the milestone have sig/ labels
Enforcing that all non-trivial PRs in the milestone have associated issues
As a result, we should be able to guarantee that all PRs are associated with a sig (not actually true since these policies started around code freeze), but can we try to generate release notes such that they are broken down by sig.

cc @dchen1107 @marun @spiffxp
@david-mcmahon
Copy link
Contributor

Yes, release notes are currently organized by the different release-note-* labels. There's no reason the notes cannot be further organized by additional (sig) labels. And you can continue to sort them into the higher level general/action-required with sig sub groupings or however you like.

@xiangpengzhao xiangpengzhao mentioned this issue Oct 21, 2017
Closed
@fejta-bot
Copy link

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 29, 2017
@david-mcmahon
Copy link
Contributor

cc @roycaihw, @enisoc @jdumars

@jdumars
Copy link
Member

jdumars commented Jan 2, 2018

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2018
@jdumars jdumars added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/P3 labels Jan 2, 2018
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 2, 2018
@fejta-bot
Copy link

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
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 2, 2018
@fejta-bot
Copy link

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

marpaia pushed a commit to marpaia/release that referenced this issue Feb 21, 2019
@k8s-ci-robot
Merge pull request kubernetes#348 from justaugustus/charter
669e029 
Update SIG info (contact info / charter)
@justaugustus justaugustus added sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Dec 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@justaugustus @jdumars @grodrigues3 @david-mcmahon @k8s-ci-robot @fejta-bot