diff options
| author | Jeffrey Sica <jeef111x@gmail.com> | 2019-09-05 11:09:04 -0400 |
|---|---|---|
| committer | Jeffrey Sica <jeef111x@gmail.com> | 2019-09-06 10:15:33 -0400 |
| commit | 2649c77cfde4314020481d73b6cbe35e6daf78fe (patch) | |
| tree | 094582d604f7063b036491d66ed3858c5e326bab | |
| parent | 74da24746810e25c41f4176a6845f97743ed5705 (diff) | |
add more milestone info to release doc
| -rw-r--r-- | contributors/devel/sig-release/release.md | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/contributors/devel/sig-release/release.md b/contributors/devel/sig-release/release.md index 3cfa1624..dac921e5 100644 --- a/contributors/devel/sig-release/release.md +++ b/contributors/devel/sig-release/release.md @@ -136,6 +136,22 @@ feature work for the given release has been defined in suitable planning artifacts in conjunction with the Release Team's [enhancements lead](https://git.k8s.io/sig-release/release-team/role-handbooks/enhancements/README.md). +After enhancement freeze, applying milestones to PRs and Issues is +important. Items within the milestone are used as a punchdown list to +complete the release. Milestones **must** be applied correctly and managed +aggressively to properly gauge what will go into a release and what +effort may be needed and when. + +What would qualify to go into a current milestone? Any item that is +required for, or slated to go into, the current release. These could +be issues or PRs in repos including (but not limited to): + +- kubernetes/enhancements +- kubernetes/kubernetes +- kubernetes/release +- kubernetes/sig-release +- kubernetes/website + Implementation and bugfixing is ongoing across the cycle, but culminates in a code freeze period: * The **code freeze** starts in week ~10 and continues for ~2 weeks. |