Flag/block/serialize silos affecting same project

[Paweł Stołowski]

From time to time we end up in a situation where QA approves two conflicting silos and in order to land, one of them needs rebuilding. The warnings about missing changelog entries happen too late in the process (usually when it passed autopkg tests and QA, and landing is attempted).

This undermines QA efforts, therefore I'd like to suggest the following enhancements to bileto:

1) clearly flag silos affecting same projects as conflicting in the Bileto dashboard.
2) block or display a warning whenever a developer/tester wants to change the state of one of the conflicting silos:
   - it shouldn't be allowed to have two conflicting silos in 'QA approved' state
   - it shouldn't be allowed for developer to mark a silo 'Lander approved' if there is a conflicting silo and it's 'Lander approved', 'QA approved' or pending publishing.

I probably missed some other possibilities.. In general it would be nice if Bileto was clever and helped as avoid clashes between silos and flag them as soon as possible.

[Robert Bruce Park (robru)]

these all sound like reasonable suggestions.