http://bugs.winehq.org/show_bug.cgi?id=60241 --- Comment #20 from Stian Low <wineryyyyy@gmail.com> --- (In reply to Rafał Mużyło from comment #19)
This bug is a *wine* bug. The fact that a discussion about wine bug wrangling policies has arisen while discussing bug's merits is irrelevant. Perhaps making a copy of this bug to discuss those would be reasonable, but changing bug component to an unrelated topic borders on vandalism.
Whatever allows this to remain open and appear in folks search results when seeking worthy bugs to work is most relevant. Any other lesser relevant topics raised were in service of that most relevant goal. I was unaware any such code analysis tools like Coverty were commonplace part of workflows so the discussion has been informative. Maybe Coverty is used in a less official way because it seems to be missing from mention by the wiki. Resistance to this bug seems primarily caused by being a bug about bugs vs just one of them but auto creating one bug per report seems impractical vs addressing each more manually and vetting on case-by-case basis. If a tool like Coverty were made more official and part of Gitlab workflow then the report of bugs/findings may be available officially from Gitlab. Then it may be reasonable for someone to create a bug to resolve all Gitlab/Coverty or alt-tools findings. It may also be reasonable for folks to create separate bug reports per items as individually addressed and link them to that wider report/effort to resolve all findings.
Of course, I'm not a part of the team, so that's just my personal, twisted opinion on the current state of things.
Nor do I have trust/privileges to change Bugzilla despite always being driven in service of whatever optimizes folks Bugzilla search results. Luckily Bugzilla supports much of that effort without needing elevated privileges. Thanks to reporter for the help raising awareness and igniting a relevant conversation about how to manage such a report going forward. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.