diff options
| author | Jeffrey Sica <jeef111x@gmail.com> | 2019-11-11 12:10:26 -0500 |
|---|---|---|
| committer | Jeffrey Sica <jeef111x@gmail.com> | 2019-11-11 12:10:26 -0500 |
| commit | 31407f3badb2f248b6373a9c6d15c5dd4e89f4f3 (patch) | |
| tree | 68bab3dd286c3ab2b728183c15891c353e17b17d | |
| parent | 2649c77cfde4314020481d73b6cbe35e6daf78fe (diff) | |
update language from guin's suggestion
| -rw-r--r-- | contributors/devel/sig-release/release.md | 39 |
1 files changed, 25 insertions, 14 deletions
diff --git a/contributors/devel/sig-release/release.md b/contributors/devel/sig-release/release.md index dac921e5..ad83ede7 100644 --- a/contributors/devel/sig-release/release.md +++ b/contributors/devel/sig-release/release.md @@ -136,21 +136,32 @@ 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 +After enhancement freeze, tracking milestones on 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 +complete the release. *On issues*, milestones must be applied correctly, via +triage by the SIG, so that release team can track bugs and enhancements (any +enhancement related issue needs a milestone) + +There is some automation in place to help automatically-assign milestones to +PRs. This automation only applies to the following repos: + +* kubernetes/enhancements +* kubernetes/kubernetes +* kubernetes/release +* kubernetes/sig-release +* kubernetes/test-infra + +**On PRs against the master branch**, milestones are auto-applied so +this is less necessary. + +**On PRS against anything not master** the milestone +requirement is absolute and iron-clad necessary. + +Any other effort that +should be tracked by the release team that doesn't fall under that +automation umbrella should be have a milestone applied. + +*"Milestone early and milestone often. Everyone will be happier."* Implementation and bugfixing is ongoing across the cycle, but culminates in a code freeze period: |