https://bugs.winehq.org/show_bug.cgi?id=56443
--- Comment #13 from Zeb Figura z.figura12@gmail.com --- (In reply to Somewhat Cold from comment #10)
Well, I don't know what to do now. I reported 3 bugs already related to this launcher, all using Wine Staging. Two of them were fixed, and this is the last one. I suppose I could try removing Staging and always use the Development version from now on. But, should I do it after this bug is fixed? Were the fixes for this bug that were just made in Staging even applied in the Development branch? Should I avoid using Staging as my main WINE? I don't know. I'm kind of new to this.
I would not recommend Wine-Staging unless you have something that specifically needs it, personally.
As a maintainer of Wine-Staging and the person who ends up responding to most bug reports, I can say that I will almost always ask if the bug is present in upstream Wine as well—since we basically want Wine bugs to be under Wine and Wine-Staging bugs to be under Wine-Staging. The latter are very specifically my responsibility, and I'd like to shunt off that responsibility whenever I can ;-)
So while we accept Wine-Staging bug reports, filing a report where only Staging was tested will generally result in a request to test upstream anyway, unless I can find a clear sign that the bug is in one place or the other.
With that said, I don't think Ken Sharp's question of "why are you using Staging" is very useful. The answer is generally "because it's commonly perceived to have more features than upstream Wine". I think that perception is not (anymore) very true, and in any case Staging is mostly targeted fixes for known applications anyway. But just asking "why" is not really an efficient way to communicate that fact.