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

prepare kinder workflows for k/k branch rename #2733

Open
neolit123 opened this issue Jul 26, 2022 · 5 comments
Open

prepare kinder workflows for k/k branch rename #2733

neolit123 opened this issue Jul 26, 2022 · 5 comments
Labels
area/kinder Issues to track work in the kinder tool kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. 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.
Milestone
Next

Comments

@neolit123
Copy link
Member

neolit123 commented Jul 26, 2022 •
edited
Loading

looks like the k/k branch will be renamed from master to main on august 3rd. edit: 9th ?

https://groups.google.com/a/kubernetes.io/d/msgid/dev/CAOxYG4wipNHR4rAC6SVH8%2BVoQj84Xum%2BTrTRwhsSm3Vjz%3D0KwQ%40mail.gmail.com?utm_medium=email&utm_source=footer

we have to update the source code of https://github.com/kubernetes/kubeadm/tree/main/kinder/ci/tools/update-workflows which hardcodes "master". then run kinder/hack/update-workflows.sh and pr k/test-infra and k/kubeadm.
@neolit123 neolit123 added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/kinder Issues to track work in the kinder tool labels Jul 26, 2022
@neolit123 neolit123 added this to the v1.25 milestone Jul 26, 2022
@neolit123
Copy link
Member Author

looks like it was postponed to 1.26 after discussions

@neolit123 neolit123 modified the milestones: v1.25, v1.26 Jul 27, 2022
@wangyysde
Copy link
Member

wangyysde commented Oct 14, 2022 •
edited
Loading

cc @wangyysde

@neolit123 neolit123 modified the milestones: v1.26, v1.27 Nov 21, 2022
@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 Feb 19, 2023
@SataQiu
Copy link
Member

SataQiu commented Feb 20, 2023

/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 Feb 20, 2023
@neolit123 neolit123 modified the milestones: v1.27, v1.28 Apr 17, 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 Jul 16, 2023
@neolit123 neolit123 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 Jul 16, 2023
@neolit123 neolit123 modified the milestones: v1.28, Next Jul 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/kinder Issues to track work in the kinder tool kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. 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.
Projects
None yet
Milestone
Next
Development

No branches or pull requests
5 participants
@neolit123 @SataQiu @k8s-ci-robot @wangyysde @k8s-triage-robot