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

Issue 880622 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
█ abdulsyed@chromium.org
gov...@chromium.org
█ cma...@chromium.org
█ pras...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

blockerbot didn't add Merge-TBD to my bug

Project Member Reported by sdy@chromium.org, Sep 4 
I landed a fix on July 27th for a bug that was M=69 and Target=69. M69 had branched, but I never got a Merge-TBD comment on the bug so I never tried to merge it.

Comment 1 by gov...@chromium.org, Sep 4

Cc: abdulsyed@chromium.org cma...@chromium.org
Blockerbot only adds TBD label if "Release Block" label is applied to the bug along with milestone labels, Few example - https://bugs.chromium.org/p/chromium/issues/list?can=1&q=OS%3DWindows%2CMac%2CLinux%2CAll+Merge%3DTBD+M%3D70&sort=pri&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

+ abdulsyed@ & cmasso@

Comment 2 by sdy@chromium.org, Sep 4

Labels: -Type-Bug Type-Feature
Oooh. I didn't realize this. I assumed it would always reply based on the text:

> We noticed that this issue is targeted for M-XX; it appears the fix may have landed after branch point, meaning a merge might be required.

Maybe this is a feature request, then?

Comment 3 by sdy@chromium.org, Sep 11 

I chatted with ellyjones@ about this, and we had the idea that:

- If a bug has a Target-* label, it might be reasonable for the bug to act regardless of blocker status.
- If a bug just has an M-* label, the meaning of that is ambiguous enough that the current behavior makes sense.

Thoughts?
►

Sign in to add a comment