Issue metadata
Sign in to add a comment
|
Migrate google_apis/drive/base_requests.cc to network service |
||||||||||||||||||||||||||
Issue descriptiongoogle_apis/drive/base_requests.cc is a dependency of chrome/browser/sync_file_system/drive_backend/sync_engine.cc. base_requests.cc uses net::URLFetcher and net::URLRequestContextGetter (through StoragePartition::GetURLRequestContext). It should be migrated to using network service's SimpleURLLoader and StoragePartition::GetNetworkContext().
,
May 14 2018
,
May 16 2018
dxie@: can you please clarify why this qualifies as P1? If so, there should be an active owner assigned. Otherwise, please adjust priority.
,
May 17 2018
dxie@: friendly ping, thanks.
,
May 18 2018
np. this is a P1 because this is needed for shipping network service to canary. See go/s13n-bug-process.
,
May 18 2018
,
May 18 2018
Thx! As per chromium triage best practices, P1 bugs should have an active owner. Does your team also follow this convention? Also, to manage expectations and avoid surprises, are you expecting that the sync team will assign resources to this effort? I'm afraid this bug doesn't qualify as P1 for our team team so we cannot commit to having resources in the short term.
,
May 28 2018
dxie@ friendly ping!
,
Jun 4 2018
Removing Services>Sync since this doesn't seem to be about Chrome Sync. Also assigning dxie@ for now, since all P1s should have an owner.
,
Jun 4 2018
marking this as available. Will follow up this week in triage to see which team will move forward with this.
,
Jun 25 2018
|
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by xunji...@chromium.org
, May 8 2018