Feedback on secondary architecute promotion requirements draft

[Kevin Kofler]

Miloslav Trmač wrote:
> AFAICT there is a clear FESCo consensus that the list can not be
> exhaustive.

That's good news.

> Essentially, asking for a promise to promote automatically if a
> checklist is met is equivalent to asking for permission to promote
> even if the software is known to be broken and/or unfixable.

+1

Promotion MUST be a case by case decision!

        Kevin Kofler