Skip to content

Commit

Permalink
PerfSheriff: update link for triage backlog
Browse files Browse the repository at this point in the history
The current link is a go link, which only works on @google account whereas most perf sheriffs will
be working from @chromium accounts, so using a direct link is better.

Change-Id: I3a277a67733b6af06aa19c42e61a22e502cce936
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422188
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#830567}
  • Loading branch information
npm1 authored and Commit Bot committed Nov 24, 2020
1 parent 81304b8 commit 7d19683
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions docs/speed/perf_regression_sheriffing.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,9 +62,10 @@ issues:
## Follow up on Performance Regressions

Please spend any spare time driving down bugs from the [regression
backlog](http://go/triage-backlog). Treat these bugs as you would your own --
investigate the regressions, find out what the next step should be, and then
move the bug along. Some possible next steps and questions to answer are:
backlog](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=Performance%3DSheriff+Type%3ABug+modified-before%3Atoday-6&sort=-modified).
Treat these bugs as you would your own -- investigate the regressions, find out
what the next step should be, and then move the bug along. Some possible next steps
and questions to answer are:

* Should the bug be closed?
* Are there questions that need to be answered?
Expand Down

0 comments on commit 7d19683

Please sign in to comment.