From dd11bd3097247d7a2b82129357e8dcda37af78c9 Mon Sep 17 00:00:00 2001 From: Roman Tsisyk Date: Tue, 7 Jan 2025 20:25:38 +0000 Subject: [PATCH] Update docs/RELEASE_MANAGEMENT.md Co-authored-by: Konstantin Pastbin Signed-off-by: Roman Tsisyk --- docs/RELEASE_MANAGEMENT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/RELEASE_MANAGEMENT.md b/docs/RELEASE_MANAGEMENT.md index 18053e1bfd..f011e9152b 100644 --- a/docs/RELEASE_MANAGEMENT.md +++ b/docs/RELEASE_MANAGEMENT.md @@ -28,7 +28,7 @@ The general recommendation is to merge large changes immediately after the relea Each release has one person appointed as the Release Manager to oversee the upcoming release. -It is the duy of Release Manager to drive the enture process to the successful completion, utilizing all available resources and means. Specific tasks may be delegated to individual team members as required. +It is the duty of the Release Manager to drive the entire process to the successful completion, utilizing all available resources and means. Specific tasks may be delegated to individual team members as required. The person holds the authority to make final decisions on cut-off and release dates, and can exclude or revert changes to ensure the release schedule is met.