http://bugs.winehq.org/show_bug.cgi?id=31374
--- Comment #66 from Jan Buecken jb.faq@gmx.de 2013-07-11 16:55:05 CDT --- Tried to find good words for a while now - did not find them - anyway:
I want to start with a question that hopefully brings us a step ahead:
What can we (the community) deliver to fix the bug? Logs, debug output? (Don't tell me to send a patch, I want a serious answer. I think there are people out there who know gdb and similar things but not the (dwrite) wine code.)
I think this is the place to work on bugs, independet when they will be fixed.
So I'm sorry that I mention my own opinion in the following lines, but I found some points that took my breath.
@ Jerome
It's 100% irrelevant how Linus or anyone else might react in a
different project. He just forgot the <sarcasm> quotes. Me too.
Wine is in the release candidate stages and that's simply too late for major features like these.
Of course. Following this strictly, incomplete features should be disabled!
As for disabling it by default, that's not going to happen.
Your last statement is contrary to this statement.
@Rosanne:
Well, I think that gets into the question of what purpose, if any, the "stable" branch serves. From what I've observed, it seems to serve two purposes: a security blanket for users who need one, and a reason to impose a code freeze once in awhile. Nobody cares about the first reason except the silly people who fall into that category.
<sarcasm on> This category does not exits since they do not get a security blanket since there is no difference between wine dev and wine stable <sarcasm off>
As for the second reason, since the issue here is completing an incomplete new feature, I suspect that code freeze means it can't be worked on until after 1.6 is released.
And now I found a contrary in your statment, too. What does "code freeze" mean? For me it means: All known bugs should be worked on and new features cannot go in the new release. On the one hand you can say this is an existing feature since 1.5.10, so it should be fixed for 1.6. On the other hand you can say this is a new feature. But then it should be disabled in 1.6 since incomplete new features cannot go in 1.6. That does the code freeze tells us.