>You want stable software, don't you?
Yes but not for the price of developing 10 years for a software.
>And break other Applications.
Not urgently
Hey guys can't anybody see the reason? The wine project (or the finish of itself) could bring linux the breakthrough. I know a lot of people who asks as first question: Is this or the other app working on linux? Then I will think about a migration.
Yes, faster development is paid by a less of stability. But is wine currently stable? By many tests with windows apps could I recognize that it is not ever!
We should make a weekly public list of currently working applications (out of the box). I strongly think this is the measurement of the development progress of wine. This is is also the only thing users are interested in! So if the developers has a huge effort to develop things in wine but the count of working apps is not increasing over the time so its a strong indicator that something goes wrong. Think about commercial software dev projects they have milestones and deadlines and they have to fulfil it. Why not making hard milestones and a hard deadline which the project itself can measure against it . Lets say the deadline of a version 1.0 is end of next year (2008-01-01). So if everybody has this deadline in brain, it meight make the whole thing a bit more efficient. Its easier to make hard priority decisions.
Roland
Yes but not for the price of developing 10 years for a software.
>And break other Applications.
Not urgently
Hey guys can't anybody see the reason? The wine project (or the finish of itself) could bring linux the breakthrough. I know a lot of people who asks as first question: Is this or the other app working on linux? Then I will think about a migration.
Yes, faster development is paid by a less of stability. But is wine currently stable? By many tests with windows apps could I recognize that it is not ever!
We should make a weekly public list of currently working applications (out of the box). I strongly think this is the measurement of the development progress of wine. This is is also the only thing users are interested in! So if the developers has a huge effort to develop things in wine but the count of working apps is not increasing over the time so its a strong indicator that something goes wrong. Think about commercial software dev projects they have milestones and deadlines and they have to fulfil it. Why not making hard milestones and a hard deadline which the project itself can measure against it . Lets say the deadline of a version 1.0 is end of next year (2008-01-01). So if everybody has this deadline in brain, it meight make the whole thing a bit more efficient. Its easier to make hard priority decisions.
Roland
>----- Ursprüngliche Mail ----
>Von: Detlef Riekenberg <[EMAIL PROTECTED]>
>An: Roland Kaeser <[EMAIL PROTECTED]>
>CC: Jim White <[EMAIL PROTECTED]>; wine-devel@winehq.com
>Gesendet: Samstag, den 16. September 2006, 19:16:34 Uhr
>Betreff: Re: AW: Already Error while installing MS Office 2003
>
>Von: Detlef Riekenberg <[EMAIL PROTECTED]>
>An: Roland Kaeser <[EMAIL PROTECTED]>
>CC: Jim White <[EMAIL PROTECTED]>; wine-devel@winehq.com
>Gesendet: Samstag, den 16. September 2006, 19:16:34 Uhr
>Betreff: Re: AW: Already Error while installing MS Office 2003
>
>On Sa, 2006-09-16 at 06:34 +0000, Roland Kaeser wrote:
>> Why don't just accept the code?
>You want stable software, don't you?
>
>> There is enough time later to make it more "beautiful" or correct it
>> to a better quality.
>Who will do it later?
>Nobody!
>
>> But for the moment, some of the code directly allows important apps to
>> work.
>
>And break other Applications.
>
>
>--
>
>By by ... Detlef
>> Why don't just accept the code?
>You want stable software, don't you?
>
>> There is enough time later to make it more "beautiful" or correct it
>> to a better quality.
>Who will do it later?
>Nobody!
>
>> But for the moment, some of the code directly allows important apps to
>> work.
>
>And break other Applications.
>
>
>--
>
>By by ... Detlef
