diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-10-25 13:43:32 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-10-25 13:43:32 -0700 |
| commit | b7ba018cab97681ef0a70be9be484eff88a43e32 (patch) | |
| tree | afcac9ab3dacd55aa9ec5b6099dbfbb494241404 | |
| parent | 1e2f1d9c6397608605bae11ab19ac7f4a6087ec8 (diff) | |
| parent | 9980ad316250f5b2fb446476f2da9b57be99c87d (diff) | |
Merge pull request #2849 from nikopen/patch-1
Features -> Enhancements
| -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..4cab95db 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://git.k8s.io/sig-release/release-team/role-handbooks/enhancements/README.md). 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 |