The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/85bf190d18689ad2466771fb99b0d353aa25e5ae

commit 85bf190d18689ad2466771fb99b0d353aa25e5ae
Author: rsleevi <rsleevi@chromium.org>
Date: Mon Jun 12 15:51:58 2017

Remove PuChuangSiDa as a known Certificate Transparency Log

As noted on
https://groups.google.com/a/chromium.org/forum/#!topic/ct-policy/M-rhwDQ1h9E
, the log has failed to abide by the uptime requirement.

BUG= 731836 
TBR=eroman@chromium.org

Review-Url: https://codereview.chromium.org/2932093002
Cr-Commit-Position: refs/heads/master@{#478639}

[modify] https://crrev.com/85bf190d18689ad2466771fb99b0d353aa25e5ae/net/data/ssl/certificate_transparency/log_list.json

Already have approval to merge two log_list.json changes that happened after this (crbug.com/692782,  crbug.com/703700 ), but one of them conflicts with this change. Can I get approval to merge this change as well, to simplify the process?

Pending LGTM from rsleevi@/awhalley@ of course.

This bug requires manual review: M60 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This is an opportunistic merge of a data-only change with no user impact.

Good for M60

Please add appropriate OSs.  Thanks.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/317ac81885617d1f3d0d3f18175fbfec65c2ee9f

commit 317ac81885617d1f3d0d3f18175fbfec65c2ee9f
Author: Eran Messeri <eranm@google.com>
Date: Thu Jul 06 10:57:32 2017

Remove PuChuangSiDa as a known Certificate Transparency Log

As noted on
https://groups.google.com/a/chromium.org/forum/#!topic/ct-policy/M-rhwDQ1h9E
, the log has failed to abide by the uptime requirement.

BUG= 731836 
TBR=eroman@chromium.org

Review-Url: https://codereview.chromium.org/2932093002
Cr-Original-Commit-Position: refs/heads/master@{#478639}
Review-Url: https://codereview.chromium.org/2966373003 .
Cr-Commit-Position: refs/branch-heads/3112@{#527}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}

[modify] https://crrev.com/317ac81885617d1f3d0d3f18175fbfec65c2ee9f/net/data/ssl/certificate_transparency/log_list.json

Can we please make sure to not merge until Merge-Approved-60 label is applied? We need to ensure that Release Owner has provided approval. 

Marking bug as Merge-Approved-60. 

My bad, sorry, I was under the impression it was approved, as it's similar to a few other merge requests mentioned above.

Sorry about that, I too saw "Good for M60" and missed the fact that the approval hadn't actually been granted yet.

My fault, sorry - should have been more explicit.