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

Issue 614588 link

Starred by 7 users

[Tracking bug] Launch MD Settings to Dev channel on Mac/Windows/Linux

Project Member Reported by tbuck...@chromium.org, May 25 2016

Issue description

This will block on all Mac/Windows/Linux issues, as well as general issues.
 
Blockedon: 614758

Comment 2 by dbeam@chromium.org, May 26 2016

Blockedon: -546841
Blockedon: 614265

Comment 4 by dbeam@chromium.org, May 31 2016

Blockedon: 604517
Blockedon: 617287
Blockedon: 613126
Blockedon: 617364
Blockedon: 617737
Blockedon: 617243
Blockedon: 608647
Blockedon: 617186
Blockedon: 618755
Blockedon: 618561
Blockedon: -595580
Blockedon: 569761
Blockedon: 614566
Blockedon: 619738
Blockedon: -613126
Blockedon: 619786
Blockedon: 621373
Blockedon: -621373
Blockedon: 611826
Blockedon: 621390
Blockedon: 621245
Blockedon: 622037
Blockedon: 622172

Comment 27 by dbeam@chromium.org, Jun 27 2016

Cc: groby@chromium.org pawli...@chromium.org
these are the bugs that must be fixed before shipping to DEV
Blockedon: -619786
Blockedon: 626845
Blockedon: 627474
Blockedon: 628502
Blockedon: -622172
Blockedon: -621245
Blockedon: 623587
Blockedon: 629447
Blockedon: 624281
Blockedon: 630505
Blockedon: 632443
Blockedon: -629447
Blockedon: -626845
Blockedon: -614758
Blockedon: 643022
Blockedon: 643394
Blocking: 649551
Blockedon: 650951
Blockedon: 654089

Comment 47 by dbeam@chromium.org, Oct 13 2016

Blockedon: 632376

Comment 48 by dbeam@chromium.org, Oct 14 2016

Blockedon: 655742
Blockedon: 639718
Blockedon: 654943
Blockedon: 654940
Blockedon: 626619
Blockedon: 656838
Blockedon: 647487

Comment 55 by dbeam@chromium.org, Oct 18 2016

Blockedon: 633520
Blockedon: 657150
Blockedon: 657960
Blockedon: 658060
Blockedon: 658075
Blockedon: 658413
Blockedon: 657215

Comment 62 by dbeam@chromium.org, Oct 26 2016

Blockedon: 653791
Blockedon: 659865

Comment 64 by dbeam@chromium.org, Oct 27 2016

Blockedon: -659865
Blockedon: 660192
Blockedon: 659259
Blockedon: 649174
Blockedon: -649174
Blockedon: -626619
Blockedon: 662491
Blockedon: 662493
Blockedon: 663507
Blockedon: 663587
Blockedon: 663588
Blockedon: 597984
Blockedon: 662919
Blockedon: 664070

Comment 78 by dbeam@chromium.org, Nov 15 2016

Blockedon: 665081

Comment 79 by dbeam@chromium.org, Nov 15 2016

Blockedon: 665082

Comment 80 by dbeam@chromium.org, Nov 17 2016

Blockedon: 653501

Comment 81 by dbeam@chromium.org, Nov 17 2016

Blockedon: -663587

Comment 82 by dbeam@chromium.org, Nov 17 2016

Blockedon: 652666

Comment 83 by dbeam@chromium.org, Nov 17 2016

Blockedon: -652666

Comment 84 by dbeam@chromium.org, Nov 17 2016

Blockedon: 654588

Comment 85 by dbeam@chromium.org, Nov 18 2016

Labels: M-56

Comment 86 by dbeam@chromium.org, Nov 18 2016

I say we go to dev and deal with suboptimal "controlled by" indicators for a week or whatever
I support this, with the following rationale/theory

"Controlled by" indicators are mostly affecting enterprise managed users, which are most likely on Stable and not Dev. Yes, I understand that extensions can also control various settings, but my theory is that enterprise policy controlling is more popular than extension controlling, so it would be OK to not block Dev launch on perfecting "controlled by" indicators.

Comment 88 by dbeam@chromium.org, Nov 18 2016

note: both policy and extensions are common to internal audiences.  i've been working on these things in priority order with a certain company's noisy bug filers in mind ;)
Blockedon: 668294
Blockedon: 668295
Status: Fixed (was: Assigned)
Blocking: -649551
Blockedon: 649551

Sign in to add a comment