Sorry for cross posting to the wine-devel but I think this may interest the whole wine community.
Selon Phil Krylov phil.krylov@gmail.com:
Fine :) Could you please correct the corresponding To Do entry on the Web site?
I can't do it right now, so I'll fix that later. Any way our To Do Section is not flexible enough.
So that raises a good question: how shall we handle bug reports?
My propositions:
1) Every bug reports handled by darwine@bugzilla.opendarwin.org or the darwine@sf Bug Management System.
2) Every bug reports handled by bugzilla.winehq.org.
3) - Wine related bugs (including darwin port specific bugs) handled by bugzilla.winehq.org. - bugs that are darwine related and not wine specific (WineHelper bugs, installer bugs, sdk bugs, ... ) handled by darwine@bugzilla.opendarwin.org or darwine@sf.
Solution 1) is the worst, since we'll have to deal with bug duplication between the darwine BMS and the winehq BMS.
Solution 2) is doable but probably not desired.
So I think we should go for 3). Whereas it seems to be the most confusing solution for bug reporters, the separation wine code/darwine distrib is clear. Anyway bug reporters usually read the "how to bug report" before submitting a bug, do they?
Would solution 3) be acceptable?
Pierre.
-
Pierre d'Herbemont