Comment 3 for bug 1983630

Cirtainly any kind of block would need to be in the clients as well to stop us failing things, so it may as well be in the client. For us it would also need to be in our automation tooling to stop that asking. sru-release is the obvious home for that.

The main issue with a blanket stop (for us) would be that kernels are nominally independant, and the freezes typically are only required for seeded packages. This makes getting an appropriate block in place hard without over-blocking and leading to a natural "--unblock" always ending up on all your command lines.

In the case in of point-release breakage; we really shouldn't be releasing without coordination and for kernel we have a team member in the loop with the release-team throughout; typically they are waiting for regressions in kernels to be resolved before they can spin (sadly).

Will start some discussion on this regardless.