From 31d29fe4e74bd989c09622d300cc56f013d3e75c Mon Sep 17 00:00:00 2001 From: Jared Watts Date: Thu, 2 Aug 2018 16:24:44 -0700 Subject: [PATCH] release: update release approval policy to be in accordance with governance Signed-off-by: Jared Watts --- build/release/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build/release/README.md b/build/release/README.md index bb5a29e73..c5aeb402a 100644 --- a/build/release/README.md +++ b/build/release/README.md @@ -37,7 +37,7 @@ The maintainers have the responsibility of ensuring this criteria is met. * Upgrade * The upgrade guide is fully walked through with all optional components from the previous **official release** to the release candidate in master, using a multi-node cluster with devices, directories, and provider specific settings. * Sign-off - * All maintainers have given their approval for the release. If unavailable, advance approval is okay. Approval can be verbal or written. + * Maintainers have signed-off (approved) of the release in accordance with the [project governance voting policy](/GOVERNANCE.md#conflict-resolution-and-voting). If a maintainer is unavailable, advance approval is okay. Approval can be verbal or written. ## Tagging a new release