Fedora Release Engineering
overview philosophy contributing troubleshooting architecture sop
This page contains information about the Fedora Release Engineering team.
Mailing List: email@example.com
Issue tracker: Fedora Releng Pagure Tickets
If you want the to get something done (e.g. moving packages to buildroots or into frozen compositions) by the ReleaseEngineering Team, please create a ticket in the issue tracker mentioned above. Please enter your FAS-username or e-mail address in the respective textbox, to make sure the team can contact you.
Release Team members are approved by FESCo. However, FESCo has delegated
this power to the Release Team itself. If you want to join the team,
Why we do things the way we do them
For information on the Fedora Release Engineering Philosophy, see
Fedora Release Engineering Leadership
Mohan Boddu (mboddu on IRC, FAS username mohanboddu)
Leadership is currently appointed by FESCo with input from the current release team.
Things we Do
- Create official Fedora releases.
- Fedora Products
Report progress towards release from branched creation on.
Give reports to FESCo on changes to processes.
If something is known to be controversial, we let FESCo know before implementing otherwise implementation generally happens concurrently to reporting.
Set policy on freeze management
Administrate the build system(s)
Remove unmaintained packages from Fedora
Push updated packages
write and maintain tools to compose and push Fedora
Joining Release Engineering
Much of rel-eng’s communication is via IRC. One of the best ways to initially get involved is to attend one of the meetings and say that you’re interested in doing some work during the open floor at the end of the meeting. If you can’t make the meeting times, you can also ping one of us on IRC or sign up for the mailing list.
Since release engineering needs special access to systems essential to Fedora people new to rel-eng will usually get access a little bit at a time. Typically people won’t immediately be granted the ability to sign packages and push updates for example. A couple of tasks you could start out with are troubleshooting why builds are failing (and if rel-eng could take actions to fix it) as the requests are submitted to pagure or help with scripts for various rel-eng tasks.
There are also a number of tools that Fedora Release Engineering uses and relies upon, working on improving these upstream to fascilitate with new things that the Fedora Project is aiming to deliver is also a great way to get involved with Fedora Rel-Eng.
How we do it
Standard Operating Procedures <sop> for details on how we do
the things we do.
Most discussions regarding release engineering will happen either in
#fedora-releng or on the releng mailing list. For
requests, please consult the
rel-eng holds regular meetings every Monday at 14:30 UTC in #fedora-meeting-3 on the Libera IRC network.
Meeting agendas are created from open tickets in pagure that contain the meeting keyword.
Minutes are posted to the rel-eng mailing list. They are also available at the Meetbot team page for releng
There are also historical Meeting Minutes for 2007-04-16 to 2009-05-04.
See our ticket queue for the things we are currently working.
See Releases for information about Fedora releases, including schedules.
String Freeze Policy (Same time as Alpha Freeze)
Change freeze policy (that’s 'Change' as in 'feature')
Updates Policy (not technically a freeze, but of interest)
Want to help? Learn how to contribute to Fedora Docs ›