From 8dba961793d40b09495592c4afe8b9d780a21912 Mon Sep 17 00:00:00 2001 From: Stefan Bueringer Date: Thu, 10 Nov 2022 08:02:06 +0100 Subject: [PATCH] docs: Add note about dependency bumps to Beta change policy MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Stefan Büringer buringerst@vmware.com --- docs/release/release-cycle.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/release/release-cycle.md b/docs/release/release-cycle.md index 90fc02dde9d0..ef4082b28e49 100644 --- a/docs/release/release-cycle.md +++ b/docs/release/release-cycle.md @@ -18,6 +18,8 @@ A release cycle can be split up into the following phases: * Providers can start adopting the new release based on the beta releases * All changes that impact providers' adoption of the new release should be announced in the provider updates section of the office hours meeting notes and approved in the PR or issue by both approvers and key affected providers. + * Non-breaking dependency bumps which don't require provider changes don't have to be explicitly approved + in addition to the regular PR review. * Week 15-16: RC * The release branch is created * Weekly RC releases will be released based on the release branch