summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-ci-robot <k8s-ci-robot@users.noreply.github.com>2018-04-25 09:39:02 -0700
committerGitHub <noreply@github.com>2018-04-25 09:39:02 -0700
commit7725a9311658df6449273fd0dbf761ceba999941 (patch)
tree8fcf9719cd3db4c4cac531ea6bc819374aca0640
parentba5c87a3c95e1ec622122b4de0f3a490d738db40 (diff)
parent42541a79687d70ae1112795ebf400addead335c6 (diff)
Merge pull request #2073 from pmorie/governance-requirements-typo
Fix typo in governance requirements doc
-rw-r--r--committee-steering/governance/sig-governance-requirements.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/committee-steering/governance/sig-governance-requirements.md b/committee-steering/governance/sig-governance-requirements.md
index ac398e1e..e5e621c0 100644
--- a/committee-steering/governance/sig-governance-requirements.md
+++ b/committee-steering/governance/sig-governance-requirements.md
@@ -64,7 +64,7 @@ All technical assets *MUST* be owned by exactly 1 SIG subproject. The following
- *SHOULD* define a level of commitment for decisions that have gone through the formal process
(e.g. when is a decision revisited or reversed)
-- *MUST* How technical assets of project remain healthy and can be released
+- *MUST* define how technical assets of project remain healthy and can be released
- Publicly published signals used to determine if code is in a healthy and releasable state
- Commitment and process to *only* release when signals say code is releasable
- Commitment and process to ensure assets are in a releasable state for milestones / releases