[ACTION REQUIRED] Kubernetes 1.12 Features Collection is underway!

[Stephen Augustus]

Hey Kubernetes peeps,

We're actively in the Features Collection process for the Kubernetes 1.12 Release.

What this means is we'll be looking to you all as Feature Owners and SIG Leads to be updating the states of active features within the kubernetes/features repo[1].

Please review the below email that was sent out to SIG Leads on 6/27 to get more details on the process and the information we'll need from you.

If you have any questions, please feel free to reach out to me on Kubernetes Slack (@justaugustus). I'll be hanging out in #sig-release and #sig-pm.

Happy shipping!

Stephen

--

Stephen Augustus

Kubernetes Product Management Chair // 1.12 Features Lead

[1] https://github.com/kubernetes/features/

On Wed, Jun 27, 2018 at 4:31 PM Stephen Augustus <augu...@redhat.com> wrote:

Hey SIG Leads!

Hot on the heels on Kubernetes 1.11, scheduled to release later today, the Kubernetes 1.12 Release Team (CC'ed here) is already gearing up to get the bits in place for another high-quality release.

In support of that, I'd like to invite you all as SIG Leads to begin updating / creating issues in k/features[1] to track the Features you expect to be working on for the 1.12 Milestone.

As a reminder, all of the following fields MUST be filled out / updated as we cross milestones:

• One-line feature description (can be used as a release note)
• Primary contact (assignee)
• Responsible SIGs
• Design proposal link (community repo)
• Link to e2e and/or unit tests
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred
• Approver (likely from SIG/area to which feature belongs)
• Feature target (which target equals to which milestone)
• Alpha release target (x.y)
• Beta release target (x.y)
• Stable release target (x.y)

While we do have the notion of a "Feature Owner", it is ultimately the responsibility of the SIG leadership (Chairs & Technical Leads) to be able to provide accurate status for the features they shepard.

The reason these fields are all so important is that they provide the Release Team an easy way to introspect on the release as a cohesive unit (we have been using the Features Tracking spreadsheet[2] for that purpose).

That information is then carried across (manually currently) and communicated in a variety of places (Community updates, RT meetings / burndowns, media briefings), so it's imperative that it's accurate.

Please take a moment to review the documentation in the k/features repo[1] and feel free to reach out to me with any questions, comments, concerns, suggestions for improvements / clarification.

Best,

Stephen

--

Stephen Augustus

Kubernetes Product Management Chair // 1.12 Features Lead

[1] https://github.com/kubernetes/features/

[2] http://bit.ly/k8s112-features

[Stephen Augustus]

Hey k8s peeps!

Features Freeze for the Kubernetes 1.12 release cycle is fast approaching on July 31, EOD PT.

We currently have 27 Features in the 1.12 Features Tracking Sheet[1]. Of those, 17 are up-to-date for this stage in the release cycle and 10 are pending responses from Feature Owners.

Additionally, there are several issues not planned for the milestone[2] that could use an update.

Feature Owners and SIG Leads --

Please, please review your open Features and update as necessary. Details in thread below.

Any features submitted or updated post-Feature Freeze will require an exception[3] to be accepted into the 1.12 Milestone.

As always, feel free to reach out to me if you have questions; @justaugustus on k8s Slack[4]. I'm hanging out in #sig-release :)

Happy shipping!

Stephen

--

Stephen Augustus

Kubernetes Product Management Chair // 1.12 Features Lead

[1] http://bit.ly/k8s112-features

[2] https://github.com/kubernetes/features/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+-milestone%3Av1.12+-label%3Atracked%2Fno

[3] https://github.com/kubernetes/features/blob/master/EXCEPTIONS.md

[4] http://slack.k8s.io

[Stephen Augustus]

Hey everyone!

It's that day that we're all excited about (...or maybe just me?).

Today is Features Freeze for the Kubernetes 1.12 Release Cycle.

Since my last email, we've gone from 27 tracked features to 54 features, which is pretty exciting!

Features Owners and SIG Leads --

Please take some time to review the Features that belong to your SIG and leave myself and the Features team a note on whether or not you plan on introducing or graduating a Feature in Kubernetes 1.12.

Here are the ones that I'm currently curious about:

• Marked as 1.12, but still waiting on info[1]
  
• Features with no milestone and no recent response to pings[2] 

Any issues in those two categories without the appropriate information by EOD PT today will require an Exception[3] to be filed.

As always, feel free to reach out to me if you have questions; @justaugustus on k8s Slack. I'm hanging out in #sig-release :)

Happy shipping!

Stephen

--

Stephen Augustus

Kubernetes Product Management Chair // 1.12 Features Lead

[1] https://github.com/kubernetes/features/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+milestone%3Av1.12+-label%3Atracked%2Fyes+

[2] https://github.com/kubernetes/features/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+-label%3Atracked%2Fno+no%3Amilestone+

[3] https://github.com/kubernetes/features/blob/master/EXCEPTIONS.md