kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add more milestone info to release doc

This commit is contained in:
Jeffrey Sica 2019-09-05 11:09:04 -04:00
parent 74da247468
commit 2649c77cfd
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
contributors/devel/sig-release/release.md
View File

@ -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 planning artifacts in conjunction with the Release Team's [enhancements
lead](https://git.k8s.io/sig-release/release-team/role-handbooks/enhancements/README.md). 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 Implementation and bugfixing is ongoing across the cycle, but
culminates in a code freeze period: culminates in a code freeze period:
* The **code freeze** starts in week ~10 and continues for ~2 weeks. * The **code freeze** starts in week ~10 and continues for ~2 weeks.