FYI we are in fact working on formally setting up a WG.
Meetings: biweekly Tuesday 9am Pacific (alternating weeks with SIG Cluster Lifecycle; will be adding one additional time for better global participation)
YouTube Playlist: https://www.youtube.com/playlist?list=PL69nYSiGNLP13_zDqYfUjfLZ2Lu9a3pv-
k/community PR #2911 against sigs list
includes a draft charter.
Feedback and participation is VERY WELCOME!
Orchestration & Containers Lead
VMware Open Source Technology Center
The recent 1.12 release renewed community commentary that the project drops support of old releases too quickly. Any support discussion dovetails into the “What is Kubernetes? Kernel? Distribution?” discussion. With cloud provider and other monolith splitting you get a wider Kubernetes software bill of materials, which makes more complex test, validation, documentation, upgrades. There’s even a question of whether a shorter release cycle might be useful too or instead of long term support. So many questions, but we don’t arrive at clear answers or actions without a more formal focus.
So we propose a Long Term Support Working Group (WG LTS) to provide a cross SIG location for focused collection of stakeholder feedback. [WG LTS is simply shorter than “WG To LTS Or Not To LTS” or “WG What Are We Releasing And Why And How Is It Best Integrated, Validate, And Supported”, but should NOT be read in that shortness to imply LTS is the foregone conclusion.]
What would this working group aim to achieve?
We expect a best-case time line of discussions this fall, especially leveraging the upcoming two KubeCons, leading then to drafting of proposals and decisions in 2019.
Please see here for more information: https://docs.google.com/presentation/d/1-Z-mUNIs3mUi7AdP1KwoAVNviwKrCoo3lxMb5wzCWbk/edit?usp=sharing
Especially the latter section of “Background Details”.
We expect a large number of vigorous objectors and supporters, and encourage folks to openly express their thoughts. We will catalog responses. And we all SHOULD keep an open mind here. The point of this proposed working group is specifically to capture feedback and assess whether there is a forward path for incremental improvement to the project’s support processes.
We’re looking here and now for lazy consensus that a working group is the correct Kubernetes project forum to explore this problem space further…which is hopefully in accordance with the current process for working group formation (just changed today).
If that is achieved we’ll look at setting up discussion forums/meetings/etc.
Tim Pepper, Dhawal Bhanushali, & SIG-Release
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/6CF00E6B-98AB-4C5C-A5E0-7F7E204DAC5E%40vmware.com.
For more options, visit https://groups.google.com/d/optout.