This is a weekly report from the I&R (Infrastructure & Release Engineering) Team. It also contains updates for CPE (Community Platform Engineering) Team as the CPE initiatives are mostly tied to I&R work.
We provide you with both an infographic and a text version of the weekly report. If you want to quickly look at what we did, just look at the infographic. If you are interested in more in-depth details look at the infographic.
Week: 19 February – 23 February 2024
Read more: Infra & RelEng Update – Week 8 2024
Infrastructure & Release Engineering
The purpose of this team is to take care of day-to-day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
List of planned/in-progress issues
Fedora Infra
- Fixed: Bodhi pod restarting
- Request for central database for OpenScanHub
- Fixed: Cannot comment on gnome-control-center, cannot merge merge requests “Forbidden You have been blocked from this project”
- Completed first system being monitored by Zabbix: releng_compose cronjobs thanks to Kevin, darknao and smooge for troubleshooting help <3
CentOS Infra including CentOS CI
Release Engineering
- Fixes for unretire packages plugin
- Fixed: dozens of f39 builds mis-tagged, getting ejected from f39-stable bodhi pushes
- Fixed: Wrong f40 / f41 release info in Bodhi
- Update IoT Signing Keys for stable
- Activate python3-rpm at epel8-next in PDC and unblock in Koji
CPE Initiatives
EPEL
Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).
Updates
- Resolved fedpkg test suite errors on Python 3.12 in preparation for EPEL 10 changes
- Added libplacebo5 to EPEL 9 to resolve mpv error
Matrix Native Zodbot
With ongoing stability issues with the Matrix <-> IRC bridge and many contributors switching over to Matrix, zodbot has become increasingly unreliable. The bridge is currently shut off completely. This initiative will provide a future proof solution and allow us to conduct meetings without wasting time troubleshooting the bridge and zodbot.
Updates
- This initiative is now finished as the Zodbot is already running in Matrix for a few months and most of the initial issues were resolved
If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on Matrix.
Recent Comments