New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 711583 link

Starred by 1 user
Status: WontFix
Owner:
█ lgar...@chromium.org
Last visit > 30 days ago
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Merge HSTS preload list removals from M59 to M58

Project Member Reported by lgar...@chromium.org, Apr 14 2017 
This has happened regularly before.
- M58 -> M57 ( Issue 698067 )
- M54 -> M53 ( Issue 641449 )
- M53 -> M52 ( Issue 624953 )
- M52 -> M51 ( Issue 613292 )
- M51 -> M50 ( Issue 601561 )

We ran into an issue with M55 ( Issue 655854 ), but for M59 -> M58 it's a clean merge without those complications.

Requesting a merge of https://chromium.googlesource.com/chromium/src.git/+/3467ad55e36b4780b267826f53530e41d0ec6b09 to Chrome 58, assuming it bakes successfully next Canary.
Project Member

Comment 1 by sheriffbot@chromium.org, Apr 14 2017

Labels: -Merge-Request-58 Merge-Review-58 Hotlist-Merge-Review
This bug requires manual review: We are only 10 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop)

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

Comment 2 by abdulsyed@google.com, Apr 14 2017

Labels: -Merge-Review-58 Merge-Approved-58
Approving for M58. Please merge this after you've baked/verified this in Canary.

Comment 3 by lgar...@chromium.org, Apr 17 2017

Labels: -Merge-Approved-58
Status: WontFix (was: Assigned)
>  but for M59 -> M58 it's a clean merge without those complications.

It seems I missed the binary data update in that commit, so it's not a clean merge. Abandoning.
►

Sign in to add a comment