Mark releases as broken

[hannesg]

As a developer, I want to make sure that know-broken releases are not shipped. Currently, if I discover a broken version, I have to manually set the correct locks and watch the release cycles. I would instead like to mark releases as broken to let automation and other devs know that this release is not fit for production.

Open Questions:

• Do we need multiple taints per release? Maybe yes because we should allow deleting taints and then it could be possible to accidentally remove taints set by somebody else.
• What should we do when you mark a release as tainted that is already deployed somewhere? Probably just show a warning in the ui or something as you can always deploy a different version manually anyway.
• More importantly, what should when you mark a release as tainted that is already queued somewhere? Just remove the queue is probably sufficient.

[sven-urbanski-freiheit-com]

Another question: Should the broken flag be related to a version, or to a version and a service? Meaning, can you mark a whole commit as broken, or also one commit in a service. I think the service use case is more important, but we can discuss this.