Home

Awesome

Enhancement Tracking and Backlog

PkgGoDev Go Report Card Slack

Enhancement tracking repo for Kubernetes releases. Owned by SIG Architecture.

This repo contains issues and KEPs. These issues are umbrellas for new enhancements to be added to Kubernetes. An enhancement usually takes multiple releases to complete. And an enhancement can be tracked as backlog items before work begins. An enhancement may be filed once there is consensus in at least one Kubernetes SIG.

Is My Thing an Enhancement?

We are trying to figure out the exact shape of an enhancement. Until then, here are a few rough heuristics.

An enhancement is anything that:

It is unlikely an enhancement if it is:

If you are not sure, ask someone in the SIG where you initially circulated the idea. If they aren't sure, jump into #enhancements on Slack or ping someone listed in OWNERS.

When to Create a New Enhancement Issue

Create an issue in this repository once you:

Why Are Enhancements Tracked

Once users adopt an enhancement, they expect to use it for an extended period of time. Therefore, we hold new enhancements to a high standard of conceptual integrity and require consistency with other parts of the system, thorough testing, and complete documentation. As the project grows, no single person can track whether all those requirements are met.

The development of an enhancement often spans three stages: Alpha, Beta, and Stable. Enhancement Tracking Issues provide a checklist that allows for different approvers for different aspects, and ensures that nothing is forgotten across the development lifetime of an enhancement.

When to Comment on an Enhancement Issue

Please comment on the enhancement issue to:

Please do not comment on the enhancement issue to:

Enhancements Tracking Board

As of the 1.26 release, enhancements from this repo are visualized in the Enhancements Tracking Boards.

Links:

Enhancements Tracking Spreadsheet

Prior to the 1.26 release, enhancements from this repo were visualized using Enhancements Tracking Spreadsheets.

Please refer to the Enhancements Tracking Spreadsheet Archive for links to these sheets.

Procedure: TBA

Current Release Cycle

Dates and further information for the 1.28 Release

Exceptions to Enhancement Milestone Dates

The Exceptions Process is handled by the Release Team, please see their documentation for further details.

Labels

Label NamePurposeHow to use this labelWho should use this label
sig/fooDenotes the SIG(s) which owns this enhancement—e.g., SIG FooSet the label using the comment /sig foo (on a separate line)Anyone
kind/featureDenotes that the issue should be tracked as an enhancement (all enhancement issues should be marked with this label)Set the label using the comment /kind feature (on a separate line)Anyone
stage/{alpha,beta,stable}Denotes the stage of an issue in the features processSet the label using the comment /stage alpha (on a separate line)Anyone

Glossary

Please refer to the Glossary for the definition of any terminology and acronyms used in the Enhancements subproject.