Governance revisited (Wineconf report)
Jeff Latimer
lats at yless4u.com.au
Thu Sep 21 16:13:34 CDT 2006
Andreas Mohr wrote:
>>Why reinvent the wheel? If such people can spend their time chasing down the problem
>>and developing a fix for it, they sure can open a bug in bugzilla, describe theproblem
>>and attach a patch they made. How more simple can it be?
>>
>>No patches lost, no extra places to look for. And all the information describing the
>>problem. Everything in one place.
>>
>>
>
>And exactly this information should probably be stated in the wine-patches
>subscription welcome mail.
>
>"If for some reason the Wine patches you submit fail to get applied,
>then we'd appreciate you taking the effort of submitting your current patch
>as a new item at bugzilla to help us track your work properly until it's
>fully applied."
>
>
>
The next question is how long does someone wait till resorting to
Bugzilla. Depending on the criteria it could generate a fair bit of
noise in the database with a lot of patches that would normally be
accepted after a couple of goes. Who is responsible for clearing the
bug report after acceptance? Unless you are actually actively pushing
the patch for acceptance, the submitter of a patch to Bugzilla would
probably be unaware that it had been accepted.
Jeff Latimer
More information about the wine-devel
mailing list