From fddb405b235726a97eb1a4b5d6d71b3aa8f921ce Mon Sep 17 00:00:00 2001 From: Furkat Gofurov Date: Wed, 25 Oct 2023 14:24:15 +0300 Subject: [PATCH] Address review comments Signed-off-by: Furkat Gofurov --- docs/release/release-team.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/release/release-team.md b/docs/release/release-team.md index 76480ea095ee..b7b4543d1093 100644 --- a/docs/release/release-team.md +++ b/docs/release/release-team.md @@ -103,8 +103,8 @@ Before you volunteer to be part of a CAPI release team, please make certain that ## Suggestions for Team Leads - * In the first week of the release cycle, organize an onboarding session with shadows of your team (i.e CI Lead with CI team shadows) to go over the general responsibilities and expectations. - * Clearly communicate with the team shadows you are responsible for, that the majority of the work during the release cycle will be a collaborative effort. + * In the first week of the release cycle, organize an onboarding session with members of your team (i.e CI Lead with CI team members) to go over the general responsibilities and expectations. + * Clearly communicate with the team members you are responsible for, that the majority of the work during the release cycle will be a collaborative effort. * Establish an ownership rotation policy in consultation with respective team members. * Provide opportunities for team members to take the lead in cutting a release within the cycle, based on feasibility. * Define backup ownership and tasks for team members, such as: