3 ms·
Not the cause. The release team asked for KEPs for all new features in the next release and the deadline was today.
by justinsb 8y ago
Not the cause. The release team asked for KEPs for all new features in the next release and the deadline was today.
- aberoham 8y agoIndeed, someone in a separate channel explained that new sig-pm staffing is at the root of the resurgence of KEPs. Thanks justinsb, no relation to GCP's Justin Santa Barbara?
- justinsb 8y agoOh sorry - yes that's me! Disclaimer: I work for Google on GKE & Kubernetes! I thought this was more of a community question and forgot...
- spiffxp 8y agoOther way around. Hi I'm the Kubernetes 1.14 release lead, I work for Google, and I'm the guy who said "bumpy road" During the Kubernetes Contributor Summit at KubeCon Seattle last year, I made lots of noise about using KEPs, and about needing non-technical contributors to help those of us who are "organizationally challenged". In what I hope was a response, people showed up at SIG PM. See https://youtu.be/_7IIzH_4yUk?t=998 https://youtu.be/_7IIzH_4yUk?t=998, https://youtu.be/mwG2CzdCg_8?t=1389 https://youtu.be/mwG2CzdCg_8?t=1389, and https://youtu.be/mwG2CzdCg_8?t=1893 https://youtu.be/mwG2CzdCg_8?t=1893 if you want to see me rambling about it on camera I think this conversation was really kicked back up in earnest as a result of Windows node support not landing in 1.13 due to a lack of clarity on what the bar was for release. There were other enhancements that could have had a smoother landings in this and previous releases, but this was definitely when we realized we needed to overhaul and document this part of the project.
- aberoham 8y agoThank you Aaron! I'll have to write a follow-up re: `smoother landings`