Add a bot that adds M-# labels to fixed issues according to the last Bugdroid comment |
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Steps to reproduce the problem: In order to make it easier for people to understand the Chrome version in which an issue is fixed, make Bugdroid or Sheriffbot (or a new bot) add M-54 if chrome/VERSION has MAJOR=54. What is the expected behavior? More information on versions that has a fix. What went wrong? Manual M-# handing which does not always happen. Did this work before? N/A Chrome version: 53.0.2785.116 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: In case the label is wrong, since the owner gets the e-mail as well, they can remove the wrong label. But I believe the label will be correct in the vast majority of the cases.
,
Sep 26 2016
Could someone from Dev team please look into this Feature Request. Thank you.
,
Sep 26 2016
cc-ing bugdroid owner.
,
Sep 27 2016
I don't think this is really infra or monorail's problem to solve. Monorail has an API via which anyone can query for "'Chrome version: 54' -label=M-54" and apply the M-54 label to all matching bugs. This could be run as a bot, built into one of the many many pre-existing TPM triage scripts, or something else. I'm going to CC laforge/kerz to see if this is a thing that they would want, but also going to close as WontFix because I don't think anyone on infra or monorail is going to fix this. If one of the TPMs thinks this would be a good feature to have, they can re-open and assign.
,
Sep 27 2016
(Oh, and bugdroid would not be a good place for this to live. It explicitly only uses repositories as input and the issue tracker as output; it never queries the issue tracker or updates bugs without a corresponding commit in a repo.) |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by phistuck@chromium.org
, Sep 24 2016