Comment 6 for bug 1879350

So I was personally a bit going back and forth about this bug. Originally, at the very beginning, I had the wrong assumption that the dangerous builds were beta based anyway - but that was just my personal imagination!

Looking at it now, seeing Ian's comment about current actual differences between grade signed and dangerous images (in practice), I think we should just do it and build the beta dangerous images in cdimage. It is unfortunate that we can't test grade signed images, which are the actual images that we want to release, and from the release team perspective it's not good. But the certification team anyway performs manual validation on the images as part of the process, so the final grade signed images will be going through a final set of testing anyway (besides the automated runs on the dangerous ones). So I think from the acceptance criteria we should be good.
Generating grade dangerous beta images will certainly have its merits.

When asking the snapd team if maybe we could drop the dangerous edge image builds, they said they still think those are useful for quick edge testing.

As Dimitri mentioned, we will need to create a new model assertion for this + add a new CHANNEL handler to livecd-rootfs. I also agree that it would look better if we then renamed the dangerous one to dangerous-edge. This will require additional work though, since besides the steps outlined by xnox, we'd also have to re-create the dangerous edge ones to something like dangerous-edge, sign them, upload to the store and (possibly) request the removal of the 'dangerous' models (to not have cruft/leftovers).