Wiki: https://fedoraproject.org/wiki/Changes/Pandas3
Discussion Thread: https://discussion.fedoraproject.org/t/180164
**This is a proposed Change for Fedora Linux.**
This document represents a proposed Change. As part of the Changes process,
proposals are publicly announced in order to receive community feedback.
This proposal will only be implemented if approved by the Fedora
Engineering Steering Committee.
== Summary ==
Update to Pandas from 2.3.x to 3.0.x which brings in improvements to
strings handling, consistent behaviour with Copy-on-Write, removing a
number of long deprecated functionality.
== Owner ==
* Name: [[User:pbrobinson| Peter Robinson]]
* Email: pbrobinson(a)fedoraproject.org
== Detailed Description ==
The Pandas 3.0 release includes various new features, bug fixes, and
performance improvements, as well as possible breaking changes.
The pandas 3.0 release removed a functionality that was deprecated in
previous releases. Upstream recommends projects to first upgrade to pandas
2.3 to ensure your code is working without warnings, before upgrading to
pandas 3.0. Fedora has had Pandas 2.3.x in Fedora since F-42 in October
2025 without any reported issues so a year later for F-45 is makes sense to
make the jump to the Pandas 3.0.x release.
== Feedback ==
N/A
== Benefit to Fedora ==
Fedora will have the latest version of Pandas and the latest features and
enhancements and continue receiving upstream support.
== Scope ==
* Proposal owners:
** Update the python-pandas package to the latest 3.x release
** Rebuild Pandas dependent packages in Fedora against the latest
python-pandas package.
* Other developers:
** Ensure packages dependent on Pandas in Fedora are up to date and
compatible with the latest Pandas release.
== Upgrade/compatibility impact ==
See above.
== Early Testing (Optional) ==
N/A
== How To Test ==
Install the latest python3-pandas package once they arrive in the Fedora
repos and ensure that your existing dependencies and projects continue to
function. There is a [
https://copr.fedorainfracloud.org/coprs/pbrobinson/pandas3/ Copr repo with
Pandas 3.0.0] with all dependent packages rebuilt against the new version
to ease testing.
== User Experience ==
Users will have the latest version of Pandas.
== Dependencies ==
Any packages dependent on python3-pandas will be rebuilt. Some dependent
packages will need to be updated to versions that support Pandas 3.0+ and
testing for those and upstream engagement and tracking is in process to
ensure compatibility across the ~50 odd Fedora dependencies.
== Contingency Plan ==
* Contingency mechanism: Revert python-pandas back to the latest 2.3.x
release.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change), Yes/No
== Documentation ==
* [https://pandas.pydata.org/docs/whatsnew/v3.0.0.html Pandas 3.0 release
notes]
== Release Notes ==
\nUpdate to Pandas 3.x for the latest data analysis / manipulation library
for Python.
Hi Folks,
If you are a change owner for F44, your change is required to be
'Testable'[1] by February 3 as per our release schedule[2]. Please ensure
your tracker bug is updated with the latest information on the status of
your change before this date and is in a testable state.
F44 changes are also required to be 'Complete' before we enter Beta Freeze
on February 17. All change tracking bugs without the status ON_QA, CLOSED
(as in done) will be asked for a current status update in their bugzillas
and a report of incomplete changes will be provided to FESCo. Please be
aware that your change may be deferred to the next Fedora Linux release if
the work involved in the change is deemed too much to complete before Beta
freeze.
If you would like to defer your change to F45[3], please let me know and I
will update the tracking links accordingly. A full list of our current F44
change set can be found on the change set page[4].
Kindest regards,
Allison
[1]
https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_ch…
[2] https://fedorapeople.org/groups/schedule/f-44/f-44-key-tasks.html
[3] https://fedorapeople.org/groups/schedule/f-45/f-45-key-tasks.html
[4] https://fedoraproject.org/wiki/Releases/44/ChangeSet
There will be an outage starting at 2026-01-29 22:00 UTC,
which will last approximately 5 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2026-01-29 22:00 UTC'
Reason for outage:
We will be applying all updates to servers and rebooting them.
We might be doing some firmware upgrades, so when services reboot they
may be down for longer than in previous "Update + Reboot" cycles.
Affected Services:
Many services will be affected, but most should only be down for a
short time as their particular resources are rebooted.
Ticket Link:
https://forge.fedoraproject.org/infra/tickets/issues/13067
Please join #admin:fedoraproject.org / #noc:fedoraproject.org on
matrix.
Updated status for this outage will be available at:
https://www.fedorastatus.org/
Hi all,
Per the Fedora Linux 44 schedule [1], we started a mass rebuild for
Fedora Linux 44 on 2026-01-16, after addressing initial blockers
related to toolchain and dependency changes (including gcc, boost, and
related updates). The Fedora Linux 44 mass rebuild has now concluded
today.
The mass rebuild was run for the changes listed at:
https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild#Driving_Features
The rebuild was carried out in a side tag (f44-rebuild) and has been
merged into f44.
Failures from the mass rebuild can be seen at:
https://kojipkgs.fedoraproject.org/mass-rebuild/f44-failures.html
Packages still needing rebuilding:
https://kojipkgs.fedoraproject.org/mass-rebuild/f44-need-rebuild.html
A total of 1,566 packages were identified as needing rebuilds as part
of this effort.
At the end of the mass rebuild, 1,242 builds have failed and will need
to be addressed by package maintainers.
In total, 22,016 builds have been successfully tagged into f44.
We also untagged the following builds from f44, as they would
otherwise break Rawhide Compose:
- authselect-1.7.0-3.fc44
- shadow-utils-4.19.0-4.fc44
- firefox-147.0-2.fc44
- net-snmp-5.9.5.2-3.fc44
FTBFS bugs will be filed shortly for the remaining failures.
Discussions related to the Fedora Linux 44 mass rebuild took place in
the releng issue tracker:
https://forge.fedoraproject.org/releng/tickets/issues/13150
Please be sure to let Release Engineering know if you notice any
issues with the reporting. You can reach us in
#releng:fedoraproject.org on Matrix, by emailing our list [2], or by
filing an issue in Forge [3].
Regards,
Samyak Jain
Fedora Release Engineering
[1] https://fedorapeople.org/groups/schedule/f-44/f-44-releng-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://forge.fedoraproject.org/releng/tickets/issues/
Greetings.
I plan to migrate https://pagure.io/fedora-infrastructure/
over to https://forge.fedoraproject.org/infra/tickets/
next tuesday ( 2026-01-20 ) starting at 21UTC.
All existing open tickets on the pagure.io side will get a comment
noting that the ticket was moved over, the README will be updated
to note the new tracker and how to handle private issues (email
admin(a)fedoraproject.org)
Folks that often interact with infrastructure may want to login to
https://forge.fedoraproject.org and set their preferences, including
enabling email if you wish to get email notifications.
( The default is off currently, but being discussed to change in:
https://forge.fedoraproject.org/forge/forge/issues/324 )
Thanks for your patience.
kevin
Wiki:
https://fedoraproject.org/wiki/Changes/BuildAtomicDesktopsWithImageBuilder
Discussion Thread: https://discussion.fedoraproject.org/t/179631
**This is a proposed Change for Fedora Linux.**
This document represents a proposed Change. As part of the Changes process,
proposals are publicly announced in order to receive community feedback.
This proposal will only be implemented if approved by the Fedora
Engineering Steering Committee.
== Summary ==
We will switch the builds of the Fedora Atomic Desktop ISOs over from
`lorax` to `image-builder`. Additionally, we will introduce extra artifacts
(`qcow2`, raw image) for those variants where an out-of-the-box setup is
available.
== Owner ==
* Name: [[User:supakeen| Simon de Vlieger]], [[User:Siosm|Timothée Ravier]]
* Email: cmdr(a)supakeen.com, siosm(a)fedoraproject.org
== Detailed Description ==
Currently the Fedora Atomic Desktops (Silverblue, Kinoite, Sway Atomic,
Cosmic Atomic, Budgie Atomic) are built using `lorax`. We've slowly been
reducing our usage of `lorax` over time; migrating mostly to `kiwi` for
live media and disk images, and `image-builder` for artifacts that require
`ostree` or `bootc`-based content.
The Fedora Atomic Installers are `boot.iso`'s with an embedded
`ostree`-commit. These are nearly identical to Fedora IoT installer ISOs
which are already produced with `image-builder`.
For this change proposal we will switch over the pungi configuration for
the above listed variants to build their ISOs with `image-builder`,
reducing `lorax` usage more.
Additionally, since `image-builder` can produce multiple other types of
artifacts out of `ostree`-commits we will introduce a `qcow2` image for
Fedora Silverblue and Fedora Kinoite and a `raw` image for those variants
(but only for `aarch64`) to be used with `arm-image-installer` for users of
single board computers (such as the Raspberry Pi).
We would love to also enable `qcow2` and `raw` images for the other Fedora
Atomic Desktop variants but we are blocked on Anaconda's `initial-setup`
not working ([https://github.com/rhinstaller/initial-setup/pull/156
upstream issue]).
If this gets resolved before Beta Freeze we could potentially also enable
the additional artifacts for those.
== Feedback ==
None yet.
== Benefit to Fedora ==
With this change and thhttps://www.youtube.com/shorts/l4E_5Fp1v14e
additional (unrelated, but in the same area) change to [
https://fedoraproject.org/wiki/Changes/ModernizeBootISO Modernize the
boot.iso] we will reduce our usage of `lorax` and simplify our deliverable
process to be done by two tools, instead of the current three.
It will also enable (in the future) to migrate the Fedora Atomic Desktops
to be `bootc`-based either in Koji, or potentially in Konflux depending on
the timing.
The availability of `qcow2` images will make 'testdriving' Fedora Atomic
Desktops easier as users can immediately spin up a virtual machine with
them. In the same fashion, the availability of `raw` images will make it
more feasible for users to run Fedora Atomic Desktops on their `aarch64`
single board computers.
== Scope ==
* Proposal owners:
** Implement the embedding of flatpaks in `image-builder`.
** Implement the Fedora Atomic Desktop installers and disk images.
* Other developers:
** Review fedora-pungi pull-requests.
* Release engineering: [
https://forge.fedoraproject.org/releng/tickets/issues/13170 #13170]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with the Fedora Strategy:
** Easier local builds and more artifacts for Fedora Atomic Variants make
them more easily available.
** Alignment with the RHEL and CentOS build processes (which use
`image-builder`).
** Alignment with `bootc`-deliverable conversion (which uses
`image-builder`) easies future migrations.
== Upgrade/compatibility impact ==
None.
== Early Testing (Optional) ==
No.
== How To Test ==
Once the relevant pungi changes have been made Fedora Rawhide composes will
contain new ISOs. These can be used in the same fashion as current ones; so
testing would consist of ensuring that they behave functionally the same
after that point.
The new artifacts will also be part of composes after the same point; users
could download and try them out :)
== User Experience ==
User experience for Fedora Atomic Desktops will not change. A new user
experience will be available (`qcow2`, `raw`).
== Dependencies ==
There are no dependencies. The work for this change proposal *does* touch
the same areas as the [
https://fedoraproject.org/wiki/Changes/ModernizeBootISO modernization work
for the boot.iso] and might simplify the implementation of that change
proposal but is not a prerequisite.
== Contingency Plan ==
* Contingency mechanism: Revert pungi configuration changes.
* Contingency deadline: Beta freeze.
* Blocks release? No.
== Documentation ==
We will be documenting local builds of Fedora Atomic Desktops in the Fedora
Atomic Desktops documentation as part of this change; though likely *after*
the contingency point.
== Release Notes ==
N/A
Wiki: https://fedoraproject.org/wiki/Changes/Build_FCOS_on_Fedora_Konflux
Discussion Thread: https://discussion.fedoraproject.org/t/179534
**This is a proposed Change for Fedora Linux.**
This document represents a proposed Change. As part of the Changes process,
proposals are publicly announced in order to receive community feedback.
This proposal will only be implemented if approved by the Fedora
Engineering Steering Committee.
== Summary ==
We want to build Fedora CoreOS updates payloads and boot disk images in
Konflux, instead of Jenkins.
== Owner ==
* Name: [[User:jcapitao | Joel Capitao]]
* Email: jcapitao(a)redhat.com
* Name: [[User:jbtrystram | JB Trystram ]]
* Email: jbtrystram(a)redhat.com
== Detailed Description ==
In F43 we switched Fedora CoreOS to be built with [
https://fedoraproject.org/wiki/Changes/BuildFCOSUsingContainerfile podman
via a Containerfile]. We can now leverage this to move our builds into the
Fedora Konflux cluster.
We also want to leverage bootc-image-builder to build our disk images in
Konflux.
== Feedback ==
None right now.
== Benefit to Fedora ==
The main benefit is the distribution of the SBOMs and attestations of the
built artifacts to the end user. One will have the ability to verify how
the OS was generated from the source code to the distribution.
Another nice side effect is that Konflux keeps the intermediate builds
artifacts in a public namespace, which makes reproducing tests failures and
debugging easier for the Fedora CoreOS maintainers.
Furthermore, this reduce the load on the Fedora CoreOS Jenkins pipeline,
which is currently maintained by the CoreOS team. This will also increase
the amount of shared code between CoreOS and bootc, helping with
maintenance and exercising the code more.
== Scope ==
* Proposal owners:
** Will switch Fedora CoreOS production streams (stable, testing, next) to
be built in Konflux. This change was already done for our rawhide builds as
an experiment. Proposal owner will also replace their current custom
osbuild pipeline with bootc-image-builder. Theses changes are purely
contained in the pipeline, they do not change the content of the produced
artefacts compared to now. Notably, the Konflux release pipeline must
integrate with the fedora message bus to get the artifact signed before
release.
* Release engineering:
** Enable selected projects to sign artifacts from Konflux pipelines using
Fedora signing keys.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with the Fedora Strategy:
** Migration to Konflux is part of the Fedora Stategy.
== Upgrade/compatibility impact ==
There should be no impact for users as the product of the new pipeline
(container images, disk images) should be identical.
== Early Testing (Optional) ==
N/A
== How To Test ==
The testing artifacts builds with Konflux are currently published in
https://quay.io/organization/coreos-devel.
One can rebase a Fedora CoreOS system to it with:
<pre>
rpm-ostree rebase ostree-image-signed:docker://
quay.io/coreos-devel/fedora-coreos:stable --reboot
</pre>
And observe no functional difference.
Note that the automatic updates won't work because the image is not from
the official release repo.
== User Experience ==
No visible change for users.
== Dependencies ==
== Contingency Plan ==
* Contingency mechanism: The Jenkins pipeline will stay in place as we will
rollout this progressively across Fedora CoreOS streams. We can revert to
use the historical Jenkins pipeline at any time.
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)
== Documentation ==
See: https://github.com/coreos/fedora-coreos-tracker/issues/2031
== Release Notes ==
\nFedora CoreOS images are now built into the Fedora Konflux Cluster.