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

Features -> Enhancements

This commit is contained in:
Niko Pen 2018-10-24 16:58:16 +02:00 committed by GitHub
parent 04ff155724
commit 47f57ea5bc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
contributors/devel/release.md
View File

@ -141,11 +141,11 @@ project is always stable so that individual commits can be
flagged as having broken something. flagged as having broken something.
With ongoing feature definition through the year, some set of items 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 starts ~4 weeks into release cycle. By this point all intended
feature work for the given release has been defined in suitable feature work for the given release has been defined in suitable
planning artifacts in conjunction with the Release Team's [features planning artifacts in conjunction with the Release Team's [enhancements
lead](https://github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks/features). lead](https://github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks/enhancements).
Implementation and bugfixing is ongoing across the cycle, but Implementation and bugfixing is ongoing across the cycle, but
culminates in a code slush and code freeze period: 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. command.
For the first ~4 weeks into the release cycle, the release team's 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. Slack, and SIG meetings to capture all required planning artifacts.
If you have a feature to target for an upcoming release milestone, begin a 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. Lead.
### Issue additions ### Issue additions