[PLEASE READ] A note about KEPs and Enhancements Freeze

[Stephen Augustus]

Hey kubies,

I know there has been some confusion around the KEPs process and the 1.14 Release Team's expectations.

I'm hoping to clarify some of this by describing some personas and actions required at this stage in the release cycle w.r.t. the process.

If you are...

Delivering an out-of-tree (non-kubernetes/kubernetes) enhancement:

No action required for you or the 1.14 Release Team. Just keep working on your KEPs and shipping high-quality code!

Delivering an enhancement that touches kubernetes/kubernetes:

Enhancement Freeze[1] has just passed.

The requirement was that enhancements landing in the 1.14 milestone would have a KEP that was marked as implementable and included a checklist for the Release Team to reference, that included as a baseline:

• k/enhancements issue in release milestone and linked to KEP
• KEP approvers have approved the KEP status as implementable
• Design details are appropriately documented
• Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
• Graduation criteria is in place
• "Implementation History" section is up-to-date for milestone
• Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Several enhancement issues have since been removed from the 1.14 milestone as part of Enhancement Freeze[1].

If you'd like to have your enhancement considered for the 1.14 milestone, here's what you need to do ASAP:

• Ensure you have an enhancements tracking issue opened in k/enhancements
• Ensure you have a KEP attached to that enhancements tracking issue, that fits the parameters mentioned above
• File an exception request[2]

In retrospect, we realize that when this was suggested, the decision to move forward with this requirement was not communicated widely enough and we apologize for the inconveniences this may have caused.

If not having a well-formed KEP in place prior to Enhancements Freeze was the reason your enhancement was kicked out of the milestone, then we're going to be lenient on granting your exception.

Getting everything into place within a single release cycle was sure to be bumpy, and we've still got a ways to go.

We appreciate your patience and all of the feedback we've received about improving the release and overall tracking process.

Another barrier to consumption has been documentation. 

In places, instructions for filing a KEP can be inconsistent and contradictory at times. We're actively working on cleaning up these inconsistencies[3][4][5][6][7][8].

If you have feedback on some of this work, please comment on those issues/PRs.

The project tracking board[9] for KEP Implementation will give you a better idea for what we're planning to attack w.r.t this effort. 

While our documentation is in flux, we realize that it will at times be confusing to pin down exactly what we're looking from you, the community, as KEP authors/reviewers/approvers.

That said, if you're ever stuck/blocked on something Release or KEP-related, here are some ways we can communicate...

• On PRs/issues: tag @kubernetes/kep-maintainers (this will ping Caleb, Jaice, and myself)
• General Program/Product/Project Management support: #sig-pm / kubern...@googlegroups.com
• SIG Release / Release Team support: #sig-release / kubernetes-...@googlegroups.com / kubernetes-...@googlegroups.com

Of course, if you'd prefer to chat 1:1, I'm @justaugustus on Slack. Happy to answer any questions you may have.

Thanks everyone!

Stephen

--

[1] https://github.com/kubernetes/sig-release/blob/master/releases/release-1.14/README.md#enhancements-freeze

[2] https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

[3] https://github.com/kubernetes/enhancements/pull/703

[4] https://github.com/kubernetes/test-infra/pull/10856

[5] https://github.com/kubernetes/community/issues/2245

[6] https://github.com/kubernetes/enhancements/issues/618

[7] https://github.com/kubernetes/community/issues/2724

[8] https://github.com/kubernetes/enhancements/issues/620

[9] https://github.com/orgs/kubernetes/projects/5

On Wed, Jan 30, 2019 at 6:10 PM Claire Laurence <clau...@pivotal.io> wrote:

Hello Everyone,

We are now entering Enhancements Freeze for v1.14.

The finalized list of enhancements that will be tracked in v1.14 can be found in the Enhancements Spreadsheet. A summary of the enhancements in v1.14 is as follows:

• 21 total enhancements

• 7 Alpha, 7 Beta, 7 Graduating

• 26 Removed or Deferred
  
  

Any new enhancements that are not on this list will require filing an exception.  We understand a few of issues are missing KEPs, if this was the reason your issue was removed from the 1.14 milestone please file an exception and for 1.14 we will be lenient if KEP was the reason.

Thank you to all the enhancement owners that took time to respond to their issues and help get this release on the right track.

The next major milestone is Code Freeze, which is slated for Thursday, March 7th.

Thanks!

Claire

--

Claire Laurence

Technical Program Manager

Cloud R&D | New York 

--
You received this message because you are subscribed to the Google Groups "Kubernetes Milestone Burndown" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-milestone...@googlegroups.com.
To post to this group, send email to kubernetes-mil...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-milestone-burndown/CAJ6bW6M%3DgbagHOynq-SKKiES0hAOrm9Uzkg7O982Tfn%2BHO64wQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.