While upstream SSH has disabled password logins for the root user as their default configuration the past number of years and that has carried over into being the out-of-the-box behavior for many operating systems, Fedora continues allowing password-based SSH root log-ins by default. But with the next Fedora release they are thinking about changing that default behavior.

One of the latest Fedora 31 change proposals is for shipping the very latest MinGW environment and toolchain in this next Fedora Linux release for ensuring a great experience for those building Windows applications on Linux.

In the run up to the Ubuntu 19.04 release I ran various gaming/graphics benchmarks looking at different desktops and X.Org vs. Wayland sessions. Check that article out if interested in the situation while this posting is just some complementary data I did from Fedora Workstation 30 when looking at the graphics performance under GNOME Shell's X.Org and Wayland sessions.

Fedora 30 has managed to ship on time per its original release schedule and is packing globs of new features.

While yesterday it was a "No-Go" for releasing Fedora 30, the developers and testers did a stellar job over the past twenty-four hours and got Fedora into shape for releasing on-time next week Tuesday.

Red Hat's lead X.Org developer Adam Jackson is looking at reworking the VESA display code path for Fedora moving forward. The plan would entail removing some old "sketchy code" from the X.Org Server and moving to UVESAFB as the VESA-based FBDEV driver but would mean dropping support for the OpenChrome driver among other changes.

While Fedora 30 isn't even out the door yet and Fedora 32 not coming out until roughly one year from now, we already know one big change on the table: dropping Python 2 and packages depending upon it.

Today was a Go/No-Go meeting for the final release of Fedora 30 but the Linux distribution in its current state isn't ready to be released. Fortunately, a week delay hasn't been set in stone yet but will be convening tomorrow to see if the latest release candidate is ready in the next 24 hours to be promoted as final.

With the last of the MPEG-2 patents having expired last February, the Fedora / Red Hat legal team is ready to okay the shipping of MPEG-2 video support out-of-the-box in Fedora Linux at long last... But they don't yet know what implementation to use.

Yesterday marked the final freeze for the upcoming Fedora 30 distribution release. The problem with Red Hat / Fedora developers being on the forefront of contributing innovations upstream to GNOME and other key components is that often exposes them to new bugs and this cycle is no different.

Well known open-source developer Lennart Poettering has shined some light onto Fedora Workstation's packaging state that it could be beneficial reducing the set of packages installed by default.

At Monday's weekly Fedora Engineering and Steering Committee (FESCo) meeting, a number of changes pertaining to Fedora 31 were approved.

If you are looking for some motivation to try out this week's Fedora 30 beta build, it's shaping up to be another massive feature update as outlined by Red Hat's Christian Schaller.

The public beta of Fedora 30 is now available for testing as the latest installment to this Red Hat developed Linux distribution now riding with the very latest packages like the GNOME 3.32 desktop.

Another change being sought for Fedora 31 is including some newer GRUB2 modules as part of the distribution's GRUB EFI boot-loader build to provide some additional security functionality.

Earlier this month was the feature proposal for Fedora 31 to finally upgrade to Mono 5, which has been out for nearly two years for this open-source .NET environment. This feature request has been approved for Fedora 31 while it's also been decided to allow it into Fedora 30 if it can land within the next week.

Python 2 support will formally reach end-of-life on 1 January 2020 and Fedora 31 is preparing for that by working to drop packages (or parts of packages) that depend upon Python 2.

The Fedora 30 Beta was anticipated for release next Tuesday after having been under a beta freeze since 5 March, but that's not going to happen and now they are hoping to ship in early April.

The plans to ship the Wayland-ized Firefox by default in Fedora 30 have been thwarted and will now have to wait until Fedora 31 to try again.

While the DNF package manager as the "next-generation Yum" has been in development for over a half-decade and has been the default over traditional Yum for a number of Fedora releases, it's still causing headaches for some and a subset of users still desiring that DNF be renamed to Yum.

Fedora 31 will likely be enabling various GCC security hardening flags by default in trying to further enhance the security of the software in its repositories and those building software on their own Fedora systems.

Fedora 30 is aiming to ship with the Wayland native version of Firefox by default rather than relying upon XWayland. This Wayland-native Firefox has long been offered in the Fedora repository but not used as the default browser. While it's not all squared away yet, more time has been granted to get it ready for this spring update to Fedora.

While Fedora is generally known to ship the very latest upstream software with each release, Fedora has continued shipping Mono 4.8 even though Mono 5.0 shipped in May 2017. With the Fedora 31 release due out later in the year, they are finally working on switching to Mono 5.

Fedora Silverblue (formerly known as Fedora Atomic Workstation) now has support for running with NVIDIA's binary graphics driver stack.

As something that arguably should have been done long ago, developers drafting plans for Fedora 31 are planning to introduce single-package gating so packages don't actually land in Rawhide (the Fedora development repository) until they successfully pass their tests... This should help weed out broken packages in Fedora Rawhide and lead to a more usable experience for those living on Fedora's bleeding-edge while also helping along a smooth release process.

Last year Fedora's Engineering and Steering Committee approved a plan to drop packages with consistently bad security track records where these packages aren't being punctually maintained in order to address known security vulnerabilities or potentially unmaintained entirely. FESCo has now approved a set of guidelines for the process by which these packages can be retired from Fedora but still stand a chance to be re-adopted and maintained.

The work led by Red Hat's Hans de Goede the past few Fedora release cycles has culminated with a great out-of-the-box boot experience for the upcoming Fedora 30.

It soon might be easier should you find yourself trying to build Debian packages from a Fedora system.

The plan to use the Wayland-native version of Firefox by default for Fedora Workstation 30 atop GNOME has been tentatively approved by the Fedora Engineering and Steering Committee (FESCo).

Under a late change proposal for Fedora 30, the DNF package manager's "best" mode might be enabled by default.