Document how the Google Gerrit team finds changes that need LC approval
Publish the change query that the Gerrit team at Google uses to find
changes that require a Library-Compliance approval. Having this query
documented allows community members that are waiting on a
Library-Compliance approval to check that their changes shows up in this
query.
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: I96d25dcc48ec75c79962feea9163b48a9dc96dd3
Bug: Google b/217845850
Release-Notes: skip
diff --git a/Documentation/dev-processes.txt b/Documentation/dev-processes.txt
index f0fe1e5..3bd88f5 100644
--- a/Documentation/dev-processes.txt
+++ b/Documentation/dev-processes.txt
@@ -366,7 +366,10 @@
* If the library is used within Google, the version of the library must be compatible with the
version that is used at Google.
-Only maintainers from Google can vote on the `Library-Compliance` label.
+Only maintainers from Google can vote on the `Library-Compliance` label. The
+Gerrit team at Google uses this
+link:https://gerrit-review.googlesource.com/q/label:%2522Library-Compliance%253Dneed%2522+-ownerin:google-gerrit-team+status:open+project:gerrit+-age:4week+-is:wip+-is:private+label:Code-Review%252B2[change query]
+to find changes that require a `Library-Compliance` approval.
Gerrit's library dependencies should only be upgraded if the new version contains
something we need in Gerrit. This includes new features, API changes as well as bug
