buildrequest collapse

 - TODO:
   - update master/docs/manual/customization.rst

First iteration of the project.
I plan to update customization.rst.
I think your analysis is correct.

Buildset A should be failure eventually. It not weird, but the result of the collapsing. Normally if you collapsed a2 and b2 it is because ssb includes ssa. So by definition, you cannot know if failure is due to ssa or ssb. The best option is thus to fail bs A and Bs B.

That said, as dustin said, there is currently a 1:N relation ship between respectly buildset and buildrequest.
In order to implement this, we must implement a N:N relation ship. when we finish a br, we may close several bs, because of the collapsing.

So for short term, I think we should mark te bs A SUCCESS (i.e worst_status(SUCCESS, SKIPPED))

I'm not exactly sure of what are the components that are actually watching for buildset completeness. (probably components like github status).
AFAIU mail status and irc status are sending updates at build level, not buildset.