diff options
Diffstat (limited to 'Documentation/dev-processes.txt')
| -rw-r--r-- | Documentation/dev-processes.txt | 13 |
1 files changed, 11 insertions, 2 deletions
diff --git a/Documentation/dev-processes.txt b/Documentation/dev-processes.txt index e43e021fd2..175a159e60 100644 --- a/Documentation/dev-processes.txt +++ b/Documentation/dev-processes.txt @@ -208,7 +208,7 @@ available. === How to report a security vulnerability? To report a security vulnerability file a -link:https://bugs.chromium.org/p/gerrit/issues/entry?template=Security+Issue[ +link:https://issues.gerritcodereview.com/issues/new?component=1371046[ security issue,role=external,window=_blank] in the Gerrit issue tracker. The visibility of issues that are created with the `Security Issue` template is automatically restricted to Gerrit maintainers and a few long-term contributors. This means as a reporter @@ -366,7 +366,10 @@ Changes that add new libraries or upgrade existing libraries require an approval * 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 @@ -378,6 +381,12 @@ months after the branch was cut. This should happen on the master branch to ensu that they are vetted long enough before they go into a release and we can be sure that the update doesn't introduce a regression. +[[escalation-channel-to-google]] +== Escalation channel to Google + +If anything urgent is blocking that requires the attention of a Googler you may +escalate this by writing an email to Han-Wen Nienhuys: hanwen@google.com + [[deprecating-features]] == Deprecating features |