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.

Fedora 32 could be two spins lighter with two little known variants of Fedora Linux set to be removed unless maintainers step up.

One of the changes planned for Fedora 32 has been to enable EarlyOOM by default to better handle low memory situations either due to the system running with minimal RAM or under memory pressure. But the Fedora Engineering and Steering Committee has yet to reach a decision over this default.

Fedora CoreOS has graduated out of its preview state and is now considered ready for general use.

Back in December was the proposal to finally enable FSTRIM by default for Fedora 32 in benefiting solid-state storage. Today the formal approval was given by the Fedora Engineering and Steering Committee to go ahead with this long overdue change.

Python scripts may be running noticeably faster come the release of Fedora 32 in April.

Separate from the whole Python 2 removal effort with the Python 2.7 that is EOL'ed since the start of the year, Fedora 33 due out later this year is looking to be their first release dropping the even older Python 2.6 series.

A late change proposal for Fedora 32 would jump the shipped Mono package from version 5.20 to version 6.6.

Fedora Project Leader Matthew Miller has shared his vision for Fedora over the next decade and is encouraging discussions about the direction of this Red Hat sponsored Linux distribution over the next five to ten years.

This morning's Fedora Engineering and Steering Committee (FESCo) meeting approved more changes for this spring's release of Fedora 32.

While Fedora 32 is already making it so CD / DVD install issues shouldn't block releases given most users are doing USB-based installations for the past number of years, Fedora is still trying to decrease the amount of space the install media takes up regardless of CD/DVD/USB media.

For months there has been many different discussions over the Linux desktop's poor performance when under memory pressure / out-of-memory type situations. That has resulted in some upstream work so far like GNOME GLib's GMemoryMonitor as well as discussions by distribution vendors about what solutions they could enable today to help the low memory situations. Fedora 32 could begin shipping and using EarlyOOM by default to help in this area.

Fedora Linux has long been well known for always shipping with bleeding-edge GCC compiler releases even if it means a near-final pre-release, thanks in part to Red Hat's significant engineering resources to GCC and the GNU toolchain in general. With Fedora 32 it's expected to be no different with having the upcoming GCC 10 compiler.

Fedora 32 is likely to make use of systemd's sysusers.d functionality for packages declaring new system users as part of the package installation process. This change proposal is being led by Red Hat's Zbigniew Jędrzejewski-Szmek of their systemd team.

Fedora continued serving at the forefront of many Linux distribution innovations over the past decade and the largely Red Hat driven platform continued contributing their work back upstream from countless GNOME features to hardware improvements/fixes, UEFI "flicker-free boot" crossing the finish line, good hardware firmware updating support, and much more.

Adding to the interesting list of proposed features for Fedora 32 would be update-alternatives handling of /usr/bin/cc and /usr/bin/c++ to more easily and seamlessly allowing pointing them at alternative compilers.

In addition to finally enabling FSTRIM for flash-based storage devices, another arguably long overdue change slated for Fedora 32 to benefit performance is compiling packages by default with link-time optimizations (LTO) by the GCC compiler.