https://bugs.winehq.org/show_bug.cgi?id=47965
--- Comment #11 from Henri Verbeet hverbeet@gmail.com --- (In reply to David from comment #7)
time and will to attempt it. Anything that could be done to automate it so that the only real input the user need do is test their software when prompted and indicate whether it passed or failed would be a great productivity boost.
In case it helps, it's indeed not entirely trivial to build Wine yourself the first time, mostly because of 32-bit dependencies. Once you have that working though, git bisect does end up being mostly a matter of marking builds as either "good" or "bad". Also, you can run Wine from the build tree, no need to install for a bisect.
To your other point, the bug tracker isn't the ideal place for having that discussion, but I can say that many Wine developers would agree with the position that with very few exceptions, anyone reporting a bug in the bug tracker is doing the project a favour, and being rude to the people reporting those bugs is harmful to the project.