Time out jumplist update for very slow or busy OS

chrome/browser/win/OWNERS

Index: chrome/browser/win/OWNERS
diff --git a/chrome/browser/win/OWNERS b/chrome/browser/win/OWNERS
index 2621204e9e79151c701fc54a94fa50c365fc28e1..4104290db851d8254ffca6faa6937d174f664bb7 100644
--- a/chrome/browser/win/OWNERS
+++ b/chrome/browser/win/OWNERS
@@ -9,4 +9,6 @@ per-file chrome_elf_init*=robertshield@chromium.org
 
 per-file enumerate_modules_model*=finnur@chromium.org
 
+per-file jumplist*=chengx@chromium.org

[grt (UTC plus 2), 2017/04/24 09:15:07]

While I am very excited about the improvements you've been making in these
files, I think you could use some more time absorbing Chromium and Windows
styles and techniques. Feel free to ping me, gab@, and/or pmonette@ down the
road if you'd like to try again. With luck, the jumplist code will soon reach
steady-state thanks to your efforts. Please let any of us know if you think that
not being an OWNER is getting in the way of your ability to make the progress
you'd like to be making. We'll see what we can do about that.

[chengx, 2017/04/24 17:24:40]

You are right. Although I have touched a lot of code in the jumplist files, I
need to absorb more chromium/windows technique and code style to be a good
reviewer. So maybe I'll try later on. 

I had the idea of adding myself to be an owner of the jumplist code simply
because I wanted to be aware of future changes on the jumplist code. Someone
changes my code may not know why I implemented it in that way. Maybe cc'ing me
about the CLs changing the jumplist implementation if there is any in the future
is a better idea.

[Ilya Sherman, 2017/04/24 18:56:05]

The WATCHLISTS file is handy for being automatically cc'ed on CLs that affect a
certain area of the codebase =)

[chengx, 2017/04/24 19:11:38]

That's a good idea! Thanks a lot! I'll defer to grt@ on this.

+
 # COMPONENT: Internals>Core