BetaFE +1

BetaFE +1

BetaFE +1

BetaFE +1

AGREED AcceptedBetaFE

The following votes have been closed:

• Accepted BetaFreezeException (+4, 0, -0)
  • +1 by nixuser, geraldosimiao, lruzicka, kparal

I find it interesting how easy it was to obtain a Freeze Exception in this situation, for something that is not even a Fedora deliverable, but a Remix. Since this is a Remix, it could just have used an overlay repository hosted in Copr or on its own infrastructure to deliver the updated package (as I have done for Kannolo in such situations). And the request did not even mention any release criteria that would be violated if this were a release-blocking deliverable (which it is not). (And the details provided in the bug report are not just vague ("can't configure the system correctly", "have a working firstboot service"), but also incomplete (it links to 3 upstream pull requests that the update supposedly introduces, but the update has been edited multiple times to add additional upstream commits from new upstream pull requests that are not documented in the Freeze Exception request).)

Something tells me that if I had requested such a Freeze Exception for Kannolo (which is/was a Fedora Remix exactly as the Fedora Asahi Remix is), it would not have met with the same enthousiasm, would it? So why does a Remix get preferential treatment for targeting the hardware of a notoriously Free-Software-unfriendly vendor that only sells its hardware bundled with a proprietary operating system (which, for that matter, conversely only comes bundled with the hardware) and that also sells hardware (iPhone, iPad) that does not even allow you to install third-party operating systems at all (and even restricts what userspace applications you can install on them)?

I am not trying to block this Freeze Exception from going out now that it has been approved, but I would like future Freeze Exceptions coming from any Fedora Remix to be held to the same high standards, as a matter of fairness.

Kevin, you're projecting. The FE was granted precisely because Calamares is not used in any release-blocking deliverable, and therefore there's no risk involved in pushing an update for it. And obviously, since it's an installer, a 0-day update is not a viable approach. It would have been granted regardless of what spin/remix/etc it targets, that just doesn't matter.

Something tells me that if I had requested such a Freeze Exception for Kannolo (which is/was a Fedora Remix exactly as the Fedora Asahi Remix is), it would not have met with the same enthousiasm, would it?

Enthusiasm? No. It would be "sure, why not", exactly the same as in this ticket.

I would like future Freeze Exceptions coming from any Fedora Remix to be held to the same high standards, as a matter of fairness.

We have high standards for blockers. For freeze exceptions, we have general guidelines and judgement calls/common sense. You can read more about our policy at QA:SOP freeze exception bug process and you can inspect all the freeze exceptions we have given in this list. We also welcome you to participate in our blocker review meetings, any additional person present is a great help.

Release F39 is no longer tracked by BlockerBugs, closing this ticket.