mNo edit summary |
|||
Line 166: | Line 166: | ||
== Fedora Linux 39 Accepted Self-Contained Changes == | == Fedora Linux 39 Accepted Self-Contained Changes == | ||
===[[Changes/Fedora Images On Azure | Fedora Images on Azure]]=== | |||
Azure is a massive public cloud and offering an official Fedora Cloud image there would expand Fedora's user base. It also gives Fedora Cloud users more options when selecting public clouds. | |||
* Owner: Major Hayden, David Duncan | |||
* Last updated: 2023-05-11 | |||
* Status: Change accepted | |||
===[[Changes/CloudEC2ImagesNoStandardStorage | Remove standard storage option from Fedora EC2 images]]=== | ===[[Changes/CloudEC2ImagesNoStandardStorage | Remove standard storage option from Fedora EC2 images]]=== | ||
AWS offers multiple types of block storage depending on the needs of the individual user. Fedora images are uploaded with standard and gp2 currently (gp3 will replace gp2 very soon with another approved change). | AWS offers multiple types of block storage depending on the needs of the individual user. Fedora images are uploaded with standard and gp2 currently (gp3 will replace gp2 very soon with another approved change). | ||
* Owner: Major Hayden | * Owner: Major Hayden | ||
* Last updated: 2023-05-03 | * Last updated: 2023-05-03 | ||
* Status: | * Status: 100% code completed | ||
===[[Changes/CloudEC2UEFIPreferred | Register EC2 Cloud Images with uefi-preferred AMI flag]]=== | ===[[Changes/CloudEC2UEFIPreferred | Register EC2 Cloud Images with uefi-preferred AMI flag]]=== | ||
A new feature of EC2 is to be able to register AMIs with a boot mode of uefi-preferred rather than picking one of bios or uefi. In EC2, aarch64 has always been UEFI, while x86-64 started out as BIOS only and some instance types have recently begun to support booting in UEFI mode. Previously, an AMI had to pick if it was UEFI or BIOS. With uefi-preferred it allows an AMI to launch with whatever firmware stack is available for the instance type, preferring UEFI when UEFI is an option. | A new feature of EC2 is to be able to register AMIs with a boot mode of uefi-preferred rather than picking one of bios or uefi. In EC2, aarch64 has always been UEFI, while x86-64 started out as BIOS only and some instance types have recently begun to support booting in UEFI mode. Previously, an AMI had to pick if it was UEFI or BIOS. With uefi-preferred it allows an AMI to launch with whatever firmware stack is available for the instance type, preferring UEFI when UEFI is an option. | ||
* Owner: Stewart Smith David Duncan | * Owner: Stewart Smith, David Duncan | ||
* Last updated: 2023- | * Last updated: 2023-05-05 | ||
* Status: Change accepted | * Status: Change accepted | ||
===[[Changes/FontAwesome6 | FontAwesome6]]=== | ===[[Changes/FontAwesome6 | FontAwesome6]]=== | ||
Line 190: | Line 195: | ||
* Owner: Stewart Smith David Duncan | * Owner: Stewart Smith David Duncan | ||
* Last updated: 2023-04-07 | * Last updated: 2023-04-07 | ||
* Status: | * Status: 100% code completed | ||
===[[Changes/Mass Retire Golang Leaves | Mass Retire Golang Leaves]]=== | ===[[Changes/Mass Retire Golang Leaves | Mass Retire Golang Leaves]]=== | ||
As of Jan 2023, 275/1660 (17%) library only Go source packages are | As of Jan 2023, 275/1660 (17%) library only Go source packages are leaves. Overall, these packages are maintained by 35 different maintainers along with the Go SIG. These leaves(by maintainer) will be mass retired in Fedora 39. | ||
leaves. | |||
Overall, these packages are maintained by 35 different maintainers along with | |||
the Go SIG. | |||
These leaves | |||
(by maintainer) | |||
will be mass retired in Fedora 39. | |||
* Owner: Maxwell G; Alejandro Sáez Morollón; the Go SIG | * Owner: Maxwell G; Alejandro Sáez Morollón; the Go SIG | ||
* Last updated: 2023- | * Last updated: 2023-05-11 | ||
* Status: Change accepted | * Status: Change accepted | ||
===[[Changes/FedoraSilverblueBootupd | Enable bootupd for Fedora Silverblue & Kinoite]]=== | ===[[Changes/FedoraSilverblueBootupd | Enable bootupd for Fedora Silverblue & Kinoite]]=== |
Revision as of 13:48, 11 May 2023
Fedora Linux 39 Accepted System-Wide Changes
RPM 4.19
Update RPM to the 4.19 release.
Owners
- Owner: Florian Festi
Tracking
- Last updated: 2023-04-17
- Tracking bug: #2187480
- Release Notes tracker: #979
- Contingency deadline: Beta freeze
- Status: Change accepted
Changes of defaults in createrepo_c-1.0.0
Update createrepo_c to 1.0.0, new release will include change of default compression to zstd, no longer generating metadata in sqlite database format by default and simplified comps xml type in repodata.
Owners
- Owner: Aleš Matěj
Tracking
- Last updated: 2023-04-10
- Tracking bug: #2185617
- Release Notes tracker: #977
- Contingency deadline: 2023-08-01
- Status: Change accepted
MinGW toolchain update
Update the MinGW toolchain to the latest upstream stable releases.
Owners
- Owner: Sandro Mani
Tracking
- Last updated: 2023-03-09
- Tracking bug: #2176849
- Release Notes tracker: #970
- Contingency deadline: Before release
- Status: 100% code completed
Modernize Thread Building Blocks for Fedora 39
Fedora is currently shipping version 2020.3 (released July 10, 2020) of the Thread Building Blocks library. The current upstream version is 2021.8 (released December 22, 2022). The Fedora community has expressed interest in moving the TBB package to track a more modern version of the upstream.
Owners
- Owner: Thomas Rodgers
Tracking
- Last updated: 2023-03-06
- Tracking bug: #2175941
- Release Notes tracker: #969
- Contingency deadline:
- Status: Change accepted
Remove pam_console
Remove pam_console as it is not enabled by default, can be replaced by systemd and has security issues.
Owners
- Owner: Iker Pedrosa
Tracking
- Last updated: 2023-02-02
- Tracking bug: #2166692
- Release Notes tracker: #965
- Contingency deadline: Beta freeze.
- Status: Testable
Boost 1.81 upgrade
This change brings Boost 1.81 to Fedora. This will mean Fedora ships with a recent upstream Boost release.
Owners
- Owner: Thomas Rodgers
Tracking
- Last updated: 2023-01-04
- Tracking bug: #2158241
- Release Notes tracker: #946
- Contingency deadline:
- Status: Change accepted
Add Fedora Auto Firstboot Services to desktop variants
Add fedora-autofirstboot to desktop variants to run a predetermined set of tasks on first boot after post installation, notably installing codecs and cleaning up installer packages from the installed system.
Owners
- Owner: Neal Gompa
Tracking
- Last updated: 2023-02-10
- Tracking bug: #2152200
- Release Notes tracker: #936
- Contingency deadline: Final freeze
- Status: Change accepted
Python 3.12
Update the Python stack in Fedora from Python 3.11 to Python 3.12, the newest major release of the Python programming language.
Owners
- Owner: Lumír Balhar
Tracking
- Last updated: 2022-11-11
- Tracking bug: #2135404
- Release Notes tracker: #903
- Contingency deadline: TBD
- Status: Change accepted
Modernize Live Media
Modernize the live media by switching to the "new" live environment setup scripts provided by livesys-scripts and leverage new functionality in dracut to enable support for automatically enabling persistent overlays when flashed to USB sticks.
Owners
- Owner: Neal Gompa, Matt Coleman
Tracking
- Last updated: 2023-03-16
- Tracking bug: #2139918
- Release Notes tracker: #898
- Contingency deadline: Final Freeze
- Status: Change accepted
Ostree Native Container (Phase 2, stable)
Continue the work done in https://fedoraproject.org/wiki/Changes/OstreeNativeContainer but in an officially stable format, and expanded to cover more OSTree-based editions. This goes "all in" on being container-native and significantly changes the technology and user emphasis.
Owners
- Owner: Colin Walters, Joseph Marrero, Brent Baude
Tracking
- Last updated: 2023-02-22
- Tracking bug: #2151321
- Release Notes tracker: #933
- Contingency deadline: Dunno
- Status: Change accepted
KTLS implementation for GnuTLS
Acceleration of GnuTLS with software Kernel TLS (KTLS)
Owners
- Owner: František Krenželok, Daiki Ueno
Tracking
- Last updated: 2023-02-10
- Tracking bug: #2130000
- Release Notes tracker: #881
- Contingency deadline: 2023-02-21
- Status: Change accepted
SPDX License Phase 2
Second phase of transition from using Fedora's short names for licenses to SPDX identifiers in the License: field of Fedora package spec files. This phase addresses how to update the License: field for existing packages, including documenting more specific guidance on how to find licenses in a package.
Owners
- Owner: Miroslav Suchý, Jilayne Lovejoy, Neal Gompa, David Cantrell, Richard Fontana, Matthew Miller
Tracking
- Last updated: 2023-04-03
- Tracking bug: #2184184
- Release Notes tracker: #974
- Contingency deadline: Beta freeze. But it is expected that not all packages will be converted by that time and the change will continue in the next release.
- Status: Change accepted
Make DNF5 The Default
Make DNF5 the new default packaging tool. The change will replace DNF, YUM, and DNF-AUTOMATIC with the new DNF5 and new Libdnf5 library. The change will mainly impact command-line users of DNF. It is a second step after https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf.
Owners
- Owner: Jaroslav Mracek, Vendula Poncova
Tracking
- Last updated: 2023-03-09
- Tracking bug: #2166026
- Release Notes tracker: #962
- Contingency deadline: Branch Fedora Linux 39 from Rawhide
- Status: Change accepted
Changes/LegacyXorgDriverRemoval
This change removes the xorg-x11-drv-vesa and xorg-x11-drv-fbdev driver packages, and associated support code from the xorg-x11-server-Xorg package.
Owners
- Owner: Adam Jackson
Tracking
- Last updated: 2023-02-22
- Tracking bug: #2078921
- Release Notes tracker: #822
- Contingency deadline: Beta freeze seems fine.
- Status: Change accepted
DNF/RPM Copy on Write enablement for all variants
RPM Copy on Write provides a better experience for Fedora Users as it reduces the amount of I/O and offsets CPU cost of package decompression. RPM Copy on Write uses reflinking capabilities in btrfs, which is the default filesystem starting from Fedora 33 for most variants. Note that this behavior is not being turned on by default for this Change.
Owners
- Owner: Matthew Almond, Davide Cavalca, Manu Bretelle
Tracking
- Last updated: 2023-02-10
- Tracking bug: #1915976
- Release Notes tracker: #634
- Contingency deadline: Final freeze
- Status: Change accepted
Fedora Linux 39 Accepted Self-Contained Changes
Fedora Images on Azure
Azure is a massive public cloud and offering an official Fedora Cloud image there would expand Fedora's user base. It also gives Fedora Cloud users more options when selecting public clouds.
- Owner: Major Hayden, David Duncan
- Last updated: 2023-05-11
- Status: Change accepted
Remove standard storage option from Fedora EC2 images
AWS offers multiple types of block storage depending on the needs of the individual user. Fedora images are uploaded with standard and gp2 currently (gp3 will replace gp2 very soon with another approved change).
- Owner: Major Hayden
- Last updated: 2023-05-03
- Status: 100% code completed
Register EC2 Cloud Images with uefi-preferred AMI flag
A new feature of EC2 is to be able to register AMIs with a boot mode of uefi-preferred rather than picking one of bios or uefi. In EC2, aarch64 has always been UEFI, while x86-64 started out as BIOS only and some instance types have recently begun to support booting in UEFI mode. Previously, an AMI had to pick if it was UEFI or BIOS. With uefi-preferred it allows an AMI to launch with whatever firmware stack is available for the instance type, preferring UEFI when UEFI is an option.
- Owner: Stewart Smith, David Duncan
- Last updated: 2023-05-05
- Status: Change accepted
FontAwesome6
Update the FontAwesome package in Fedora to version 6.x, with a compatibility package for packages still needing 4.x.
- Owner: Jerry James
- Last updated: 2023-03-24
- Status: Change accepted
EC2 AMIs default to the gp3 EBS volume type
In Amazon EC2, Elastic Block Store (EBS) volumes can be one of several types. These can be specified at volume creation time, including for the default volumes that are created on instance launch. An AMI will have default volumes and volume types configured. Fedora currently defaults to the gp2 volume type. This proposal is to switch to gp3 as the default volume type for Fedora. The gp3 volume type is both more flexible than gp2, and can be up to 20% cheaper per GB.
- Owner: Stewart Smith David Duncan
- Last updated: 2023-04-07
- Status: Change accepted
Register EC2 Cloud Images with IMDSv2-only AMI flag
In November 2019, AWS launched IMDSv2 (Instance Meta-Data Store version 2 - see https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/ ) which provides "belt and suspenders" protections for four types of vulnerabilities that could be used to try to access the Instance Meta-Data Store available to EC2 instances. In that announcement, AWS recommended adopting IMDSv2 and restricting access to IMDSv2 only for added security. This can be done at instance launch time, or (more recently in October 2022) by providing a flag when registering an AMI to indicate that the AMI should by default launch with IMDSv1 disabled, and thus require IMDSv2.
- Owner: Stewart Smith David Duncan
- Last updated: 2023-04-07
- Status: 100% code completed
Mass Retire Golang Leaves
As of Jan 2023, 275/1660 (17%) library only Go source packages are leaves. Overall, these packages are maintained by 35 different maintainers along with the Go SIG. These leaves(by maintainer) will be mass retired in Fedora 39.
- Owner: Maxwell G; Alejandro Sáez Morollón; the Go SIG
- Last updated: 2023-05-11
- Status: Change accepted
Enable bootupd for Fedora Silverblue & Kinoite
By design, ostree does not manage bootloader updates as they can not (yet) happen in a safe fashion. To solve this issue, bootupd (https://github.com/coreos/bootupd) was created. bootupd is a small socket activated program that takes care of updating the bootloader. It currently only supports EFI booted systems and rpm-ostree based systems. The updates are triggered by an administrator and are not (yet) automated for safety reasons. This change is about enabling bootupd integration in Fedora Silverblue and Fedora Kinoite to make bootloader updates easier. bootupd is already used in Fedora CoreOS.
- Owner: Timothée Ravier, Tomáš Popela, Colin Walters
- Last updated: 2023-02-23
- Status: In progress
LXQt image for aarch64
Generate LXQt image (both iso and disk image) for aarch64 architecture.
- Owner: Zamir SUN
- Last updated: 2023-04-10
- Status: Testable
Build Fedora Silverblue & Kinoite using rpm-ostree unified core mode
rpm-ostree upstream development is focusing on the "unified core" mode and the previous mode is being deprecated. Fedora Silverblue and Fedora Kinoite are currently building using the old mode and we've wanted to move over for a while. The main advantage of the unified core mode is that it is stricter and safer, while enabling some post processing steps to happen during or after the image build.
- Owner: Timothée Ravier, Tomáš Popela, Colin Walters
- Last updated: 2023-02-23
- Status: In progress
Modular GNOME Keyring services
The monolithic daemon provided by GNOME Keyring will be split into dedicated sub-daemons, so that they can be consistently managed by systemd.
- Owner: Daiki Ueno, Benjamin Berg
- Last updated: 2023-02-13
- Status: Change accepted