Original is here: https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.or...
Future updates will be cross-posted.
-------
(This first update is big. Subsequent updates should be smaller.)
Changes:
+ Anaconda defaults to Btrfs for automatic partitioning for all desktop installation media
+ libvirtd patches have landed that will set 'nodatacow' (chattr +C) on VM image containing directories when on Btrfs, by default: virt-manager, GNOME Boxes, Cockpit, et al, will benefit from this directly; minimally tested OK, needs some further testing
+ Numerous btrfs kernel patches, related to Fedora concerns and requests have landed on upstream linux-btrfs@, including new 'rescue=all' mount option to better tolerate read-only mount despite file system damage
+ anaconda fix for Silverblue on Btrfs, set "rootflags" boot parameter so startup succeeds
+ various compose related fixes for non-ISO images; PR submitted, not yet merged into production (consequence is, these Rawhide images are not being created right now for armhfp: Workstation, KDE, Xfce, LXDE, MATE, Sugar)
+ btrfs driver is now built-in to the kernel, rather than as a module
+ Red Hat CKI (Continuous Kernel Integration) have added btrfs to their regular xfstests and will report failures upstream
Communication:
+ Fedora Magazine article(s) are in the idea and specification phase. https://pagure.io/fedora-workstation/issue/162 https://discussion.fedoraproject.org/t/btrfs-by-default/22020 https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/216?kanb...
Documentation:
+ Draft material available for review, organization and content development in-progress. https://pagure.io/fedora-workstation/issue/158
+ Clarification is needed to what degree effort should be spent on updating upstream wiki so it doesn't conflict with Fedora reality; versus Fedora specific content focus.
Noteworthy bugs:
+ Btrfs corruption tracked down to bad RAM (confirmed with memtest86+); will result in improvements to 'btrfs check --repair' to better handle this case; does also expose the difficulty with Btrfs only stating the facts rather than pointing the finger at the cause. https://bugzilla.redhat.com/show_bug.cgi?id=1857996
+ Btrfs tracking bug https://bugzilla.redhat.com/show_bug.cgi?id=1851166