Align release date calculation with documentation #12240
Conversation
To improve the predictability of release dates, it was agreed to start the stabilization phase on the last Monday of the first Month in the quarter. Consequently, the release is expected two weeks after the stabilization period is started. Signed-off-by: Marcus Burghardt <[email protected]>
marcusburghardt
added
enhancement
|
Start a new ephemeral environment with changes proposed in this pull request: Fedora Environment Oracle Linux 8 Environment |
|
🤖 A k8s content image for this PR is available at: Click here to see how to deploy itIf you alread have Compliance Operator deployed: Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and: |
|
Code Climate has analyzed commit 918149d and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 59.4% (0.0% change). View more on Code Climate. |
|
/packit test |
|
/packit rebuild-failed |
|
/test images |
|
@marcusburghardt: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description:
To improve the predictability of release dates, it was agreed to start the stabilization phase on the last Monday of the first Month in the quarter.
Consequently, the release is expected two weeks after the stabilization period is started.
Rationale:
In alignment to #12232
Review Hints: