chromium/src
0
Fork 0
Code Activity

Adding the revert of culprit CL to blocker management

Browse Source 
Change-Id: Ic6fb050cd52ae434582597970adb3eec3575f268

Bug: b/269963763
Change-Id: Ic6fb050cd52ae434582597970adb3eec3575f268
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4637743
Commit-Queue: Srinivas Sista <srinivassista@chromium.org>
Reviewed-by: Harry Souders <harrysouders@google.com>
Cr-Commit-Position: refs/heads/main@{#1161274}
This commit is contained in:
Srinivas Sista
2023-06-22 16:52:20 +00:00
committed by Chromium LUCI CQ
parent 00f8233f15
commit f7e419d42e
1 changed files with 4 additions and 0 deletions

4
docs/process/release_blockers.md

@ -150,6 +150,10 @@ are some general guidelines to follow:
* The release management team (release engineers and TPMs) have the final say
when it comes to release blocking issues - they can tag, and untag, issues
as they see fit.
* For fixing your release blockers, please consider a revert of the culprit CL as
your first option if it is safe to do so.
## Other Considerations