Johan Corveleyn wrote: > [...] a vote in STATUS does not necessarily imply that I have run the > entire testsuite across 3 ra flavours etc.
You noted current differences. Let's say the testing of all required combinations was automated. Can we examine what remains? What are your thoughts on the proposal to unify them so that a single +1 means "I approve this backport: it results in a release candidate that I approve for release"? Can we define voting requirements that satisfy the combined meaning? One issue I see is the "resulting release candidate" for a given patch depends on which patches were included before it. Whenever two or more patches are being reviewed simultaneously, we need a way to track their assumed ordering, and to re-evaluate when it changes. For example we might assume initially that each will pass the vote, and so evaluate them as if merged in order of proposal, and whenever a not-latest patch is vetoed, re-start the evaluation of all later ones. I don't see that as a problem, just something to be taken into account. - Julian
