User guide: Make clear that label functions are orthogonal to code owners
Often it is not clear that the label function "MaxWithBlock" can still
block the change submission after sufficent code owner approvals have
been applied.
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I27cb9f8efaf44b269737cca90dc9da5fa127a034
diff --git a/resources/Documentation/user-guide.md b/resources/Documentation/user-guide.md
index 4337161..f7318ee 100644
--- a/resources/Documentation/user-guide.md
+++ b/resources/Documentation/user-guide.md
@@ -230,7 +230,13 @@
**NOTE:** Besides the code owners submit rule there may be further submit rules
that block the change submission for other reasons that are not related to code
-owners.
+owners. E.g. configured [label
+functions](../../../Documentation/config-labels.html#label_function) are
+completely orthogonal to code owner approvals. If, for example, `Code-Review+1`
+votes are required as code owner approval, but the `Code-Review` label has the
+function `MaxWithBlock` the change submission is still blocked if a max approval
+(aka `Code-Review+2`) is missing or if a veto vote (aka `Code-Review-2`) is
+present.
**NOTE:** Gerrit submit rules are executed on submit and when change details are
loaded, e.g. when loading the change screen (to know whether the submit button
