donat at enikeev.net
Mon Oct 23 07:17:17 CDT 2017
> How about having a bit more strategy discussion on merging Wine Staging patches (quicker) to mainline wine?
It would be interesting video indeed, I followed several big patch series based on staging and adjusted to be well-qualified (tests, fixes, etc) -- that were moving to the bottom of https://source.winehq.org/patches/ without a comment or response and then disappeared :) Probably there are some non-obvious rules like proof-of-time or code-support concerns or existing plans to implement same functionality in a more correct way -- visibility on the staging->mainline process would be very useful for those, who want to help the project in this way, as clearly staging patches help win applications on the edge and attract attention of potential volunteers
P.s. At least, it looks as making sense to add to for each patch in staging git, what it is lacking, ideas on better implementation, links to discussions or quotes from there, etc
23.10.2017, 14:00, "Marcus Meissner" <meissner at suse.de>:
> On Mon, Oct 23, 2017 at 12:18:27AM -0600, Alex Henrie wrote:
>> 2017-10-13 5:23 GMT-06:00 Jacek Caban <jacek at codeweavers.com>:
>> > It's getting close to WineConf and I think it's time to think about agenda.
>> > Does anyone have anything he'd like to talk about? Any ideas about
>> > conversations we should have? Feel free to add them to
>> > https://wiki.winehq.org/WineConf2017
> How about having a bit more strategy discussion on merging Wine Staging
> patches (quicker) to mainline wine?
> Ciao, Marcus
More information about the wine-devel