Sheriffbot-Auto-triage Rule: Launch bugs - 3 milestones older than current stable milestone |
||||
Issue descriptionSheriffbot-Auto-triage Rule: Launch bugs - 3 milestones older than current stable milestone. Issue/Concern or feedback: Launch bugs are often associated with features that are turned on via Finch (this is the recommended best practice go/newChromeFeature) In the Finch guide (go/finch-guide), we recommend the launch bug to not be closed until the feature is fully launched and the client Finch logic has been removed. Additionally, for experiments the advise is to post an update on the results of the experiment before closing the bug. When the sheriff bot closes launch bugs as Archived, the above recommendations will be getting followed. Can we figure out a process that makes more sense? e.g. having the sheriff bot first remind the owners about the best practices on how to close the launch bug some time before it would close them. +rkaplow, who's been also working on the updated Finch guide.
,
Apr 1 2016
Starting w/ the problem statement: As a team, we tend to never close Launch bugs, which is generally problematic as most of them in the current backlog are no longer actionable. The logic for choosing the time period bomb of 4.5-6 months (3-4 milestones) of no follow-up action is that is represents a strong indication of inactivity (and that people aren't going back and following the process recommendation to close out their issues and report on the findings). A middle approach would be to add a warning + Hotlist label to note that these bugs will be Archived w/ out taking a specific action, followed by an actual Archive (say a month later) if that guidance is ignored. Thoughts on that approach?
,
Apr 5 2016
asvitkine@, could you please provide your thoughts on approach listed by laforge@ on comment #2.
,
Apr 5 2016
Warning definitely sounds good to me.
,
Apr 6 2016
OK, assigning to cdavid@, could you please make the change as listed on comment #2. Thank you.
,
Jul 22 2016
CL landed and deployed with a warning + Hotlist label as listed in comment #2. |
||||
►
Sign in to add a comment |
||||
Comment 1 by gov...@chromium.org
, Mar 30 2016Owner: lafo...@chromium.org