On Thu, Nov 11, 2010 at 08:17:58PM +0100, Macieira Thiago (Nokia-MS-Qt/Oslo) wrote: > On Thursday, 11 de November de 2010 19:53:27 Oswald Buddenhagen wrote: > > > It's what we have now and nothing changes. > > well, in fact, what we have now will merge the merge into the meanwhile > > progressed mainline branch (*), i.e., it produces "merge spam" - exactly > > the thing we don't want. but you'd have to do exactly that if you wanted > > a non-disruptive non-replaying merge process. > > Not really. One merge is enough. > no, it's not, because mainline will have progressed because of other integrations. hey, wait - that's where we started from ...
the only way around that is having no integration queue at all: the lieutenant always starts from an empty set and doesn't come back until the run has completed. that's only realistic if the modules are small enough or the branch hierarchy is deep enough for a single lieutenant (or one of his proxies) to be sufficient to do the entire job. while we certainly could do that (it's like the linux community works), it's a rather drastical departure from the way how we work today, and how the webkit community works. _______________________________________________ Opengov mailing list Opengov@qt-labs.org http://lists.qt-labs.org/listinfo/opengov
