0e9d714c76
As per September 22, 2020 meeting of SIG Release, we've decided that the working group's discussions have led to positive changes and have run their course. Remaining discussion and operational points have reasonable ownership, for example in SIG Release and WG Reliability. Signed-off-by: Tim Pepper <tpepper@vmware.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| charter.md | ||
README.md
LTS Working Group
Answer the question: Does Kubernetes need a longer support term? If yes, figure out what that looks like for Kubernetes and propose this to the rest of the project. If no, figure out how to help end users cope with this and propose that to the rest of the project. If a proposal is accepted, the working group's mission will change to implement it. The working group is sponsored by SIG Release, but has the potential to span almost all SIGs. For more background see the WG formation proposal.
The charter defines the scope and governance of the LTS Working Group.
Stakeholder SIGs
- SIG API Machinery
- SIG CLI
- SIG Node
Meetings
- Regular WG Meeting: Tuesdays at 09:00 PT (Pacific Time) (bi-weekly). Convert to your timezone.
Organizers
- Dhawal Yogesh Bhanusali (@imkin), VMware
- Quinton Hoole (@quinton-hoole), Huawei
- Tim Pepper (@tpepper), VMware
- Nick Young (@youngnick), VMware
Contact
Goals
- Evaluate user/operator sentiment and support requirements.
- Foster cross-vendor, subject matter expert led bug and security fixes for support streams. The project is more sustainable when this work is done once authoritatively in shared support branch(es), versus in parallel at all vendors.
- Increase developer visibility on cross-release compatibility and stability issues.
- If appropriate based on analysis, draft LTS KEP for SIG Release to operationalize.
We are an open and active working group, and we always welcome new additions!