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

Update KEP-1731 to include the latest implementation changes #2289

Open
xmudrii opened this issue Jul 24, 2023 · 4 comments
Open

Update KEP-1731 to include the latest implementation changes #2289

xmudrii opened this issue Jul 24, 2023 · 4 comments
Assignees
@xmudrii
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@xmudrii
Copy link
Member

xmudrii commented Jul 24, 2023

We had to make some implementation changes for KEP-1731 (publishing packages to the community infra) along the way but these changes didn't made their way to the KEP. We need to ensure that the KEP is up to date as it might be used as the implementation reference in the future.

/assign
/sig release
/area release-eng
/priority important-soon
@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 priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jul 24, 2023
@xmudrii xmudrii moved this to 🔖 Backlog in SIG Release - Packaging Jul 24, 2023
@xmudrii xmudrii added the kind/documentation Categorizes issue or PR as related to documentation. label Jul 24, 2023
@k8s-ci-robot k8s-ci-robot removed the needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label Jul 24, 2023
@xmudrii xmudrii mentioned this issue Aug 4, 2023
Closed
@xmudrii xmudrii moved this from 🔖 Backlog to 📝 Tracking Issues in SIG Release - Packaging Sep 11, 2023
@xmudrii xmudrii moved this from 📝 Tracking Issues to 🔖 Backlog in SIG Release - Packaging Sep 11, 2023
@xmudrii xmudrii moved this from 🔖 Backlog to Backlog (prioritized) in SIG Release - Packaging Nov 12, 2023
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Jan 25, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Jan 25, 2024

/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 25, 2024
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Apr 24, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Apr 24, 2024

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 24, 2024
@xmudrii xmudrii moved this from Backlog (prioritized) to 🏗️ In Progress in SIG Release - Packaging May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xmudrii xmudrii

Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
SIG Release - Packaging
Status: 🏗️ In Progress
Milestone
No milestone
Development

No branches or pull requests
3 participants
@xmudrii @k8s-ci-robot @k8s-triage-robot