need dual-queues with bisecting rollbacks

[Monty Taylor]

<mtaylor> a full regression run takes 4 hours - I can't do that on every
commit
<mtaylor> but I want to run a full platform build suite on each run
<mtaylor> so the projected thought is: on approved merge, run it through
build testing
<mtaylor> then, every so often (like every 4 hours or so) merge everytihng
that passed build testing into a single commit and then run that through
regression testing
<mtaylor> if it passes, great - if it fails _there_...
<mtaylor> then bisect the passed build revisions until you find the one that
regressioned
<mtaylor> reject that one, and move on
<mtaylor> this will come up for openstack too - because we're going to a
have functional/integration testing which will require clustering tests
across many computers - don't want to do that for _every_ merge req :)
<mtaylor> now - figuring out how to hook this back and forth with hudson
will be trickier ... since hudson is currently the one who groks how to test
builds for us across all the platforms

[Paul Hummer (rockstar)]

I'm also not sure about whether this is core or not. Bisecting them seems like a bit of extra effort that could be solved by humans just being notified. I think something like an atomic Tarmac command that would actually queue merges would be awesome, but we are running out of states to put an MP in that Tarmac can understand. If we want this, we need merge queues in Launchpad.