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.

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

Bump ISO Go version back up to 1.20 after buildroot fix #15841

Closed
spowelljr opened this issue Feb 13, 2023 · 4 comments · Fixed by #18020
Closed

Bump ISO Go version back up to 1.20 after buildroot fix #15841

spowelljr opened this issue Feb 13, 2023 · 4 comments · Fixed by #18020
Assignees
Labels
kind/process Process oriented issues, like setting up CI lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@spowelljr
Copy link
Member

Bumped Go version back down to 1.19.5 from 1.20 due in 3006b3e due to https://lore.kernel.org/buildroot/CA+h8R2rtcynkCBsz=_9yANOEguyPCOcQDj8_ns+cv8RS8+8t9A@mail.gmail.com/T/

@spowelljr spowelljr added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/process Process oriented issues, like setting up CI labels Feb 13, 2023
@XDRAGON2002
Copy link
Member

XDRAGON2002 commented Feb 16, 2023

@spowelljr Hi, I'm a new contributor and would like to resolve this issue, just wanted to confirm if the reason for downgrading has been resolved, i.e. is it okay to open a PR bumping up the version now?

/assign

@spowelljr
Copy link
Member Author

spowelljr commented Feb 16, 2023

I don't believe that buildroot has released a new version yet so I don't think any action is able to be taken yet.

https://buildroot.org/news.html

The required PR will have to bump the buildroot version and Go version in tandem.

@XDRAGON2002
Copy link
Member

Sure, I'll keep this issue on a tracking thread then.

@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 May 20, 2023
@spowelljr spowelljr 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 May 22, 2023
@XDRAGON2002 XDRAGON2002 removed their assignment Oct 1, 2023
@spowelljr spowelljr self-assigned this Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/process Process oriented issues, like setting up CI lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
4 participants