Fedora 45 delayed again, could be launched in early November at the earliest

Abstract:

The latest Go/No-Go release review meeting held by the Fedora project decided that Fedora 45 once again failed to obtain release permission. This means that the version will not only fail to launch this week according to the original early release schedule, but will also miss next week's release window, and the release time will be delayed by at least another week.

Previously, Fedora 45 had missed the Go/No-Go conference release evaluation last week because it was not ready in time for the release candidate version (Release Candidate), and therefore was not released as originally planned. At the review meeting held this week, the development team once again made a "NO-GO" decision due to the unresolved multiple critical blocking defects.

Confirmed release blocking issues include: an update is required to mitigate issues related to eMudhra; the AArch64 image size of Fedora Server 45 exceeds the specified limit; the LVM automatic activation function fails after upgrading to Fedora 45 in an environment based on LUKS encrypted physical volumes (PV); and KDE Plasma Discover incorrectly installs outdated native RPM packages from the Fedora 44 repository.

In addition to the confirmed blocking issues, the development team is evaluating three additional flaws that may be classified as release blockers. These include: failure to configure the network interface through the ip=kernel parameter during installation; the Stratis encrypted storage pool failing to start properly; and the encrypted Stratis root partition entering emergency mode after receiving no response to the password prompt.

At the same time, a small number of defects have received Freeze Exception approval, but these are not enough to resolve the critical issues currently affecting the release.

After reaching the "NO-GO" conclusion at this meeting, Fedora 45 is determined not to be released next week. According to the current plan, the new version is tentatively scheduled to be launched on November 3. However, the final release as scheduled still depends on whether these critical blocking issues can be fixed and verified within the next week.