On Friday, 23 Oct 2015 18:55:18 +0200, Sebastian Lackner wrote:
The development branch has more infrastructure for patch management than just the wine-patches and wine-devel mailing list, you also have to take into account the patch status page for example. Even the development branch of Wine, where most of the patches go upstream right on the next day, needs a way to keep track of the patch status.
[...]
I also think that the suggested solution does not hide anything from the rest of the Wine developers. The WineHQ bugtracker is publicly available to everyone, and flexible enough to configure all kind of notifications you want to receive. I would guess most people are not really interested in Staging tree related submissions, because even in the month after WineConf, I didn't receive any offers from "new people" to help cleaning up our patches for example... but if there is, it doesn't sound like something which is impossible to solve.
I have no problem with alternative suggestions, but just saying "use the mailing lists" doesn't work. Mailing lists do not replace proper patch tracking, which is what we are really talking about here.
To bring this discussion full circle, how will Staging pick up patches from wine-patches? And how will this be signified? Will the upstream patch tracker have a "Staged" status assigned by one of the maintainers?
-
Hugh McMaster