diff options
| author | Grace Nguyen <42276283+gracenng@users.noreply.github.com> | 2022-09-07 09:48:01 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-09-07 09:48:01 -0700 |
| commit | 576249b32018e46f80cabc4f5ebb862d7efe58e4 (patch) | |
| tree | c830f5cb9e8ce7d68839748bd014975b209964eb | |
| parent | a386c1b625b3dd117dfe689b0695bea5c8158430 (diff) | |
Communicate PRR freeze
| -rw-r--r-- | sig-architecture/production-readiness.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/sig-architecture/production-readiness.md b/sig-architecture/production-readiness.md index b3699d7d..17471f7b 100644 --- a/sig-architecture/production-readiness.md +++ b/sig-architecture/production-readiness.md @@ -20,6 +20,10 @@ As of 1.21, PRRs are now blocking. PRR _approval_ is required for the enhancemen to be part of the release. This means that any KEPs targeting the release for any stage will require production readiness approval by the *Enhancements Freeze Date*. +Introduced in 1.23, *Product Readiness Freeze* happens a week before *Enhancements Freeze Date*. All KEPs must be opted in by this date to help PRR reviewers provision their workload. +KEPs opted in after the *Product Readiness Freeze* are at risk +of not being reviewed by the PRR team, depending on bandwidth. + Note that some of the questions in the [KEP template] should be answered in both the KEP's README.md and the `kep.yaml`, in order to support automated checks on the PRR. The template points out these as needed. |