Tag: Fedora Infrastructure (page 2 of 6)

FMN Replacement Blog – March

It’s been about two months since our last blog post was out. The team wants to give everyone an update on our progress and let you know that we are nearly at the finish line!

Continue reading

Infra & Releng Team in 2022

Infra & Releng Team is a sub-team in Red Hat’s Community Platform Engineering (CPE) Team that takes care of Fedora Infrastructure, Fedora Release Engineering, and CentOS Infrastructure. This blog post is a summary of what the team did in 2022. It contains infographics as a quick review. Below that will be more detailed information about what you can see in the infographics.

Continue reading

CPE hiring a software engineer

The Community Platform Engineering group, or CPE for short, is the Red Hat team combining IT and release engineering for Fedora and CentOS. We currently have a position open for a software engineer in India.

Read more: CPE hiring a software engineer

About the role

We are hiring new talent to come work full time on Fedora, primarily as part of our Release Engineering group. You’ll get to work on the infrastructure that builds and ships the Fedora Linux release artifacts and updates. This role is perfect for anyone with experience or interest in Release Engineering.

About CPE

Our goal is to keep core servers and services running and maintained, build releases, and perform other strategic tasks that need more dedicated time than volunteers can give.

See our docs for more information. We are looking forward to meeting you and hopefully working with you soon!

Backwards-incompatible changes in Bodhi

The 6.0 release of Bodhi — Fedora’s update gating system — will be published in a few days. We will deploy it to production a couple weeks after the Fedora release. It includes backwards-incompatible changes. Here’s what you need to know.

Continue reading

EPEL 9 is now available

On behalf of the EPEL Steering Committee, I’m pleased to announce the availability of EPEL 9. This is the culmination of five months of work between the EPEL Steering Committee, the Fedora Infrastructure and Release Engineering team, and other contributors. Package maintainers can now request dist-git branches, trigger Koji builds, and submit Bodhi updates for EPEL 9 packages.

Instructions to enable the EPEL repository are available in our documentation. If there is a Fedora package you would like to see added to EPEL 9, please let the relevant package maintainer know with a package request.

Continue reading

Fedora program update: 2020-23

Here’s your report of what has happened in Fedora this week. Elections voting is open through 11 June.

I have weekly office hours in #fedora-meeting-1. Drop by if you have any questions or comments about the schedule, Changes, elections, or anything else.

Continue reading

CPE achievements during Q1 2020

2020 has seen a lot of changes for everyone—understatement of the year right? One of these changes has been how the Community Platform Engineering (CPE) Team has decided to adjust how they work. We are on an agile workflow journey. We began this year with quarterly planning, for the first time ever! We kicked off the start of the year working on some prioritised initiatives that we discussed as a review team during our first quarterly planning session. The review team included Brian ‘Bex’ Exelbierd, Paul Frields, Jim Perrin, Leigh Griffin, Pierre-Yves Chibon, Brian Stinson and Clément Verna.

The initiatives chosen to be worked on during Quarter One were:

  • FAS Replacement Login Phase 1 
  • Fedora Data Centre Move
  • CentOS Stream Phase 1 
  • CI/CD 
Continue reading

What’s coming up next in Fedora and CentOS infrastructure?

As you may know, the Community Platform Engineering (CPE) team that helps manage both infrastructure for both Fedora and CentOS is trying to improve how the different initiatives or requests for changes we receive are planned and prioritized. This effort to improve has led us to look at planning our work in three-month windows. By planning, limiting, and focusing our work every three months, we can dedicate a substantial team around each initiative, driving it to completion before working on the next. Overall this helps us finish and deliver work faster.

Continue reading
Olderposts Newerposts

Copyright © 2025 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑