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

Receipts process for tracking release enhancements #2140

Closed
4 tasks
Tracked by #617
palnabarun opened this issue Nov 10, 2020 · 7 comments
Closed
4 tasks
Tracked by #617

Receipts process for tracking release enhancements #2140

palnabarun opened this issue Nov 10, 2020 · 7 comments
Assignees
@palnabarun @jeremyrickard
Labels
area/enhancements Issues or PRs related to the Enhancements subproject lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/release Categorizes an issue or PR as relevant to SIG Release. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Projects
Enhancements Subproject
Milestone
v1.21

Comments

@palnabarun
Copy link
Member

palnabarun commented Nov 10, 2020 •
edited
Loading

Enhancement Description

  • One-line enhancement description (can be used as a release note): Receipts process for tracking release enhancements
  • Kubernetes Enhancement Proposal: Provisional KEP PR
  • Primary contact: @jeremyrickard @palnabarun
  • Responsible SIGs: architecture, release
  • Enhancement target (which target equals to which milestone):
    • Alpha release target: 1.21
    • Beta release target: TBD
    • Stable release target: TBD
  • Alpha
    • KEP (k/enhancements) update PR(s): TBD
    • Code (k/k) update PR(s): TBD
    • Docs (k/website) update PR(s): TBD

/assign @jeremyrickard @palnabarun
/sig architecture
/sig release
/area enhancements
/milestone v1.21
/stage alpha
@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Nov 10, 2020
@k8s-ci-robot k8s-ci-robot added sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Nov 10, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Nov 10, 2020
@k8s-ci-robot k8s-ci-robot added the area/enhancements Issues or PRs related to the Enhancements subproject label Nov 10, 2020
@palnabarun palnabarun added the tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team label Nov 10, 2020
@LappleApple LappleApple added this to In progress in Enhancements Subproject Nov 10, 2020
@palnabarun palnabarun mentioned this issue Nov 26, 2020
Closed
@annajung annajung added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Feb 2, 2021
@palnabarun palnabarun mentioned this issue Feb 4, 2021
Closed
11 tasks
@saschagrunert saschagrunert mentioned this issue Feb 9, 2021
Closed
@LappleApple LappleApple mentioned this issue Feb 22, 2021
Closed
51 tasks
@annajung annajung added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Feb 24, 2021
@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-contributor-experience at kubernetes/community.
/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 May 25, 2021
@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-contributor-experience at kubernetes/community.
/lifecycle rotten

@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 Jun 24, 2021
@k8s-triage-robot
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-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: 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-contributor-experience at kubernetes/community.
/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.

Enhancements Subproject automation moved this from In progress to Done 1.22 Jul 26, 2021
@JamesLaverack
Copy link
Member

/reopen
/remove-lifecycle rotten

@k8s-ci-robot
Copy link
Contributor

@JamesLaverack: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

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.

@k8s-ci-robot k8s-ci-robot reopened this Dec 16, 2021
@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Dec 16, 2021
@justaugustus justaugustus moved this from Done to PRs - Blocked, or Author Inactivity in +30 Days in Enhancements Subproject Dec 16, 2021
@palnabarun
Copy link
Member Author

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Dec 23, 2021
Enhancements Subproject automation moved this from PRs - Blocked, or Author Inactivity in +30 Days to Done Mar 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@palnabarun palnabarun

@jeremyrickard jeremyrickard

Labels
area/enhancements Issues or PRs related to the Enhancements subproject lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/release Categorizes an issue or PR as relevant to SIG Release. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Projects
Enhancements Subproject
  
Done
Milestone
v1.21
Development

No branches or pull requests
7 participants
@JamesLaverack @palnabarun @k8s-ci-robot @annajung @fejta-bot @jeremyrickard @k8s-triage-robot