[doc] [sheriffing] Add a note about respins to the Flaky tests section
Change-Id: If353d4c564e4b493d870b8405419df24d520f28c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2708424 Reviewed-by: Alex Mineer <amineer@chromium.org> Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#867340}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
00544945a5
commit
df4ff8f68e
@@ -80,6 +80,11 @@ to the branch in question and is not flaky on trunk, you will need to create a
|
|||||||
new CL to disable it only on the branch and go through the usual merge request
|
new CL to disable it only on the branch and go through the usual merge request
|
||||||
process.
|
process.
|
||||||
|
|
||||||
|
Note: there is little value in merging changes to the stable release
|
||||||
|
branch when the next milestone's stable release is less than a week away
|
||||||
|
(since there are usually no planned stable respins at that point).
|
||||||
|
You can find release dates on [chromiumdash][chromiumdash-schedule].
|
||||||
|
|
||||||
### Landing changes
|
### Landing changes
|
||||||
|
|
||||||
When you need to land a change to a branch, you'll need to go through [the same
|
When you need to land a change to a branch, you'll need to go through [the same
|
||||||
|
Reference in New Issue
Block a user