As one of the last minute change proposals for Fedora 33 is to introduce the Red Hat backed Storage Instantiation Daemon "SID" though at least for this first release would be off by default. The Storage Instantiation Daemon is one of the latest storage efforts being worked on by Red Hat engineers.

Fedora stakeholders are debating the merits of potentially ending legacy BIOS support for the Linux distribution and to only support UEFI-based installations.

Fedora for the past few releases doesn't show the GRUB boot-loader menu by default when only Fedora is installed on the system as there is little purpose for most users and it just interrupts the boot flow. But for those wanting to access the GRUB bootloader menu on reboot, they offer integration in GNOME to easily reboot into this menu. The other exception is the menu will be shown if the previous boot failed. This functionality has relied on downstream patches but now they are working towards a better upstream solution.

More than a decade ago Fedora was routinely trying to pursue the Btrfs file-system by default but those hopes were abandoned long ago. Heck, Red Hat Enterprise Linux no longer even supports Btrfs. While all Red Hat / Fedora interests in Btrfs seemed abandoned years ago especially with Red Hat developing their Stratis storage technology, there is a new (and serious) proposal about moving to Btrfs for Fedora 33 desktop variants.

Fedora developers are once again discussing a proposal on switching to Nano as the default text editor on Fedora systems.

A change proposal for Fedora 33 would introduce the concept of "fedora-retired-packages" for removing retired packages when upgrading Fedora.

As part of our ongoing testing of the AMD Ryzen 5 4500U and Ryzen 7 4700U "Renoir" mobile processors, here is some Wayland vs. X.Org data with the GNOME desktop on Fedora Workstation 32.

Some Fedora spins have already made use of swap on zRAM for serving as a compressed RAM drive while with Fedora Workstation 33 they are looking to make use of zRAM by default.

A feature proposal raised by Red Hat's Jeff Law would allow Fedora packages to be built under the LLVM Clang compiler rather than defaulting that all packages to be built under GCC. Clang-built packages would happen where the upstream software recommends using Clang by default or for software without an upstream to let the packager(s) make their own decision.

The Fedora Engineering and Steering Committee (FESCo) today approved the plans for Fedora 33 to enable systemd-resolved by default.

Fedora 32 has officially been released as the latest installment of this Red Hat supported community Linux distribution known for its bleeding-edge features and packages.

When it comes to finding laptops with Linux pre-loaded by the OEM, it's mostly Ubuntu or its derivatives found most often on these devices. But Lenovo and Red Hat are announcing today that Fedora Workstation 32 will begin appearing soon on select ThinkPad laptops.

After it was delayed last week, Fedora 32 will now be released next week.

Hopefully it won't be like many Fedora releases in the past that were dragged out for weeks at a time due to blocker bugs (thankfully, recent Fedora releases have been tremendously better in that regard), but Fedora 32 will not be debuting next week as planned due to bugs.

Fedora 33 this autumn is looking to make use of systemd-resolved by default rather than NSS-DNS for name resolution.

Fedora 33 later this year will see a new "Enterprise Linux Next" (ELN) buildroot and compose setup for testing new changes potentially destined for the next release of Red Hat Enterprise Linux. Most notable from the original ELN proposal is on potentially raising the x86_64 CPU requirements. ELN is now approved to take place.

To date Fedora has defaulted to Java 1.8 / OpenJDK 8 as the default system JDK version but for Fedora 33 later this year they plan to transition to OpenJDK 11.

Red Hat Enterprise Linux 9 will likely see support for older x86_64 CPUs eliminated to focus on more modern x86_64 Intel/AMD families. With that, Red Hat developers working on Fedora have been working on an "Enterprise Linux Next" proposal to not only vet such x86_64 build changes but also to provide a feedback workflow for other changes.

Fedora Project Leader Matthew Miller has sent out a reminder to Fedora contributors to "be excellent to each other" while announcing the project has a new vision statement.

With new feature work beyond the scope now of Fedora 32, we're beginning to get a better idea for some of the feature plans for Fedora 33 due out this autumn.

The beta of the highly anticipated Fedora 32 Linux distribution update is now available.

For the Fedora 33 release later this year, Red Hat is looking at further enhancing and strengthening the cryptography settings/configuration of the OS.

As a move ultimately for Red Hat Enterprise Linux as well, Red Hat developers working on Fedora are planning to transition the RPM database (RPMDB) away from the long-standing Berkeley DB to using SQLite.

Fedora 32 Beta was deemed unready for release on Thursday during the initial Go/No-Go meeting but after reconvening twenty-four hours later the remaining blocker bugs were addressed.

Fedora Project Leader Matthew Miller recently talked about his vision for the Fedora Project over the next decade and it to become an "operating system factory", among other advancements he hopes to see out of the project in the 2020s. A one-sentence vision for Fedora is now drafted as their vision statement.

Issues with Fedora's 32-bit ARM Xfce desktop spin will no longer be treated as a release blocker for the Linux distribution but instead the Fedora Workstation for 64-bit ARM (AArch64) will be considered a blocking issue.

Fedora 30 and Fedora 31 users will soon see Linux 5.5 come down as a stable update, but before then you can help if so inclined to test this new kernel revision on Fedora.

There had been a proposal to better compress the Fedora 32 install media via SquashFS without the nested EXT4 file-system setup for its live images and also ramping up the XZ compression. But this proposal was rejected at yesterday's engineering meeting on the basis that a more optimal compression path could be utilized.

Another alternative to slow initramfs generation could be distributing pre-built initramfs images to users. An additional benefit of that is possibly better security with measured boot capabilities, a matter currently being discussed by Fedora stakeholders.

Fedora IoT already uses swap-on-ZRAM by default given IoT devices are often running with limited amounts of RAM, but for Fedora Workstation 33 the developers are looking at enabling SWAP-on-ZRAM by default for all new installations.