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

Issue 862492 link

Starred by 1 user
Status: Assigned
Owner:
█ sonnysasaka@chromium.org
Last visit > 30 days ago
Cc:
snanda@chromium.org
r...@chromium.org
qiyuh@chromium.org
█ mcchou@chromium.org
█ shijinabraham@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Remove "Unfiltered Bluetooth Devices" flag

Project Member Reported by sonnysasaka@chromium.org, Jul 11 
This flag is only needed during NewBlue early development stage and should be removed by M71 which should have NewBlue more or less stable. This bug tracks the removal so we don't end up having stale flags.

Comment 1 by r...@chromium.org, Jul 11

Components: IO>Bluetooth
Labels: -Pri-2 ReleaseBlock-Stable M-71 Pri-1

Comment 2 by dgagnon@chromium.org, Sep 14 

M71 Dev approaching. Will flag be removed before M71 Dev or before M71 Stable?

Comment 3 by sonnysasaka@chromium.org, Sep 14

Labels: -M-71 M-72

Comment 4 by sonnysasaka@chromium.org, Sep 14 

Postponing to M72.

Comment 5 by harpreet@chromium.org, Oct 9

Cc: shijinabraham@chromium.org

Comment 6 by sonnysasaka@chromium.org, Dec 15

Labels: -M-72 M-73
There is still a bug in newblue's EIR parsing that has been fixed only recently. Postponing this to M73 to make sure the fix is right.
►

Sign in to add a comment