diff options
| author | Niko Pen <42466421+nikopen@users.noreply.github.com> | 2018-10-24 16:58:16 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-10-24 16:58:16 +0200 |
| commit | 47f57ea5bc48626da07de00a91f00708a27b213d (patch) | |
| tree | 07f5759be77f11fe6c93fe4f321c18f3aa486df7 /contributors | |
| parent | 04ff155724d9722d69dfcecc56ebf1170b01519f (diff) | |
Features -> Enhancements
Diffstat (limited to 'contributors')
| -rw-r--r-- | contributors/devel/release.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/contributors/devel/release.md b/contributors/devel/release.md index 49df8e4c..efb53b4a 100644 --- a/contributors/devel/release.md +++ b/contributors/devel/release.md @@ -141,11 +141,11 @@ project is always stable so that individual commits can be flagged as having broken something. With ongoing feature definition through the year, some set of items -will bubble up as targeting a given release. The **feature freeze** +will bubble up as targeting a given release. The **enhancement freeze** starts ~4 weeks into release cycle. By this point all intended feature work for the given release has been defined in suitable -planning artifacts in conjunction with the Release Team's [features -lead](https://github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks/features). +planning artifacts in conjunction with the Release Team's [enhancements +lead](https://github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks/enhancements). Implementation and bugfixing is ongoing across the cycle, but culminates in a code slush and code freeze period: @@ -232,11 +232,11 @@ milestone by creating GitHub issues and marking them with the Prow "/milestone" command. For the first ~4 weeks into the release cycle, the release team's -Features Lead will interact with SIGs and feature owners via GitHub, +Enhancements Lead will interact with SIGs and feature owners via GitHub, Slack, and SIG meetings to capture all required planning artifacts. If you have a feature to target for an upcoming release milestone, begin a -conversation with your SIG leadership and with that release's Features +conversation with your SIG leadership and with that release's Enhancements Lead. ### Issue additions |