release: update release approval policy to be in accordance with governance
Signed-off-by: Jared Watts <jbw976@gmail.com>
This commit is contained in:
1 file changed
+1
-1
@@ -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
|
||||
|
||||
|
||||
Reference in new issue
Block a user