-
Notifications
You must be signed in to change notification settings - Fork 632
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
K3s incubation proposal #1307
base: main
Are you sure you want to change the base?
K3s incubation proposal #1307
Conversation
Signed-off-by: Chris Wayne <cwayne18@gmail.com>
@cwayne18 sorry i have to point to an old issue from 2020 here - k3s-io/k3s#2245 |
@dims that's a fair call-out, we have reduced the number of commits we carry over time, and the majority of the remaining commits are either irrelevant to upstream or very k3s specific. That said, we can do another audit and try to push any applicable commits upstream. Is this something that would/should block this proposal? |
thanks @cwayne18
No. |
I'm very good at spelling. Co-authored-by: Olivier Vernin <olivier@vernin.me> Signed-off-by: Chris Wayne <cwayne18@gmail.com>
It appears that the new process for proposal is opening an issue instead of a PR, would y'all prefer I close this out and open an issue instead? |
Thanks for checking @cwayne18 - yes, the new issue template is preferred though not required - it will ultimately be up to the TOC member who picks up the due diligence. If you do fill out the new issue - the project's place in the queue will be maintained. |
Thanks so much! Sorry if I appear impatient, I'm just checking to make sure I follow whatever process works best for y'all! I'll start the work to convert it over and update some of the metrics. Thanks again! |
K3s proposal to graduate from Sandbox -> Incubating