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

Reducing Build Maintenance in CIP #2818

Closed
4 tasks
tylerferrara opened this issue Jul 9, 2021 · 4 comments
Closed
4 tasks

Reducing Build Maintenance in CIP #2818

tylerferrara opened this issue Jul 9, 2021 · 4 comments
Assignees
@justaugustus @listx @tylerferrara
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Milestone
v1.22

Comments

@tylerferrara
Copy link
Contributor

tylerferrara commented Jul 9, 2021 •
edited by justaugustus
Loading

Enhancement Description

  • One-line enhancement description (can be used as a release note):
    Reducing Build Maintenance in CIP

  • Kubernetes Enhancement Proposal:
    KEP-2818: Reducing Build Maintenance in CIP #2817

  • Discussion Link:
    WG K8s Infra Meeting

  • Primary contact (assignee):

  • Responsible SIGs: @kubernetes/release-engineering

  • Enhancement target (which target equals to which milestone):

    • Alpha release target (x.y):
    • Beta release target (x.y):
    • Stable release target (x.y):

  • Alpha

    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
cc: @listx @amwat @justaugustus @kubernetes/release-engineering
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jul 9, 2021
@tylerferrara tylerferrara mentioned this issue Jul 9, 2021
Merged
@justaugustus
Copy link
Member

/assign @tylerferrara @listx @justaugustus
/sig release
/area release-eng

@k8s-ci-robot k8s-ci-robot 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 and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 17, 2021
@justaugustus justaugustus 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 Aug 17, 2021
@justaugustus justaugustus added this to the v1.22 milestone Aug 17, 2021
@salaxander salaxander added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Aug 19, 2021
@k8s-triage-robot
Copy link

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

This bot triages issues and 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 issue is closed

You can:

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

Please 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 Nov 17, 2021
@justaugustus justaugustus removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Dec 2, 2021
@justaugustus
Copy link
Member

This is implemented and the KEP PR has merged: #2817
Thanks Tyler for your work here!
/close

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Closing this issue.

In response to this:

This is implemented and the KEP PR has merged: #2817
Thanks Tyler for your work here!
/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justaugustus justaugustus

@listx listx

@tylerferrara tylerferrara

Labels
area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. tracked/out-of-tree Denotes an out-of-tree enhancement issue, which does not need to be tracked by the Release Team
Projects
None yet
Milestone
v1.22
Development

No branches or pull requests
6 participants
@justaugustus @listx @salaxander @k8s-ci-robot @tylerferrara @k8s-triage-robot