Comment 10 for bug 1980180

Thank you for shedding some light on the topic, Simon! And thank you for uploading the new version of calamares. It's a bit on me for not engaging in this topic earlier, and now we're in this weird situation where we're trying to land things very late for .1.

That being said, since both Lubuntu and Studio leads, so the only flavors currently using calamares, are +1 on having this for .1, I am willing to get this SRU landed and trying to ship it with .1. It's a risky move, so I'd like to set some ground rules here:
 * I will review and (hopefully) accept the calamares packages today, making them build in -proposed
 * I'll kick a manual build using -proposed of the affected flavors and ping for testing here and on IRC. I would appreciate a quick look by flavors to assess if there is nothing bad with the update - would be welcome if validation flags would be switched here
 * If all looks good, we promptly promote the calamares packages to jammy-updates tomorrow (on a Friday, oh no!). This should be fine as this is basically only an installer package, so no worries about breaking existing users
 * But since the -proposed validation period is so short, some of the real-life-validation will most probably have to happen with the RCs for .1. So the rule is: if we find a critical regression with the new calamares, we revert back to the old package and rebuild, since that's the only 'safe' way to proceed. Other options are delaying the .1 release (which I don't think is feasible) or skipping flavors (...I don't think anyone wants that either!)

Hope this plan is okay. I'll start working on it in a moment.