Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=1801539 ** Information from BlockerBugs App:
Commented but haven't voted yet: lbrabec
The votes have been last counted at 2025-03-10 18:20 UTC and the last processed comment was #comment-960210
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
I would definitely like to see new OSTree installs have trim enabled by default, but we've apparently been shipping this way since Silverblue 31. I don't think this passes "the last blocker" test for me.
FinalBlocker -1
Discussed during the 2025-03-10 blocker review meeting [1]:
!agreed 1801539 - Rejected as a Final Blocker - Silverblue is not a blocking deliverable, so we can't consider it here. IoT should be affected by this in theory, but in practice it seems unlikely that full disk encryption is used at scale there, by our estimate. Also, many SD cards (used in IoT) might not even support trim. Additionally, this problem has been around for 5 years already, further weakening the blocker proposal. We will document this as a CommonBug instead.
[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-03-10/f42-blocker-review.2025-03-10-16.01.log.html
AGREED RejectedFinalBlocker
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F42 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.