ReleaseEngineering

This page contains information about the Fedora Release Engineering team.

Contact Information

 * IRC: #fedora-releng
 * Mailing List: rel-eng@lists.fedoraproject.org
 * Issue tracker: https://fedorahosted.org/rel-eng/newticket

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.

Composition

 * Dennis Gilmore (dgilmore) (Leader)
 * Jesse Keating (f13)
 * Bill Nottingham (notting)
 * Rex Dieter (rdieter)
 * Kevin Fenzi (nirik)

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, contact the releng team using the contact information above.

What is Fedora Release Engineering?
Broad Overview

Who's in Charge
Dennis Gilmore (dgilmore on IRC, FAS username ausil). Leadership is currently appointed by FESCo with input from the current release team.

Things we Do

 * Set the schedule for releases including freeze dates, final release, slips, etc.
 * Set blocker criteria for the release.
 * Decide what packages go onto a spin.
 * Create official Fedora Spins.
 * Report progress towards release from Feature Freeze 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)

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 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) or taking care of buildroot overrides as the requests are submitted to trac.

How we do it
See our  Standard Operating Procedures for details on how we do the things we do.

Most discussions regarding release engineering will happen either in #fedora-devel or on the fedora-devel-list mailing list. For requests, please consult the contact information above.

Meetings
Meetings are regularly held every Friday at 1700 UTC. Our meetings are held in #fedora-meeting on the Freenode IRC network. At times we will have meetings more often than the scheduled times, particularly if a release is coming up. Meeting notes will be posted to fedora-devel-list and the wiki below.


 * Meeting agendas are created from open tickets in Trac

Meeting Minutes

 * http://fedoraproject.org/wiki/ReleaseEngineering/Meetings

Current activities
See our ticket queue for the things we are currently working.

See Releases for information about Fedora releases, including schedules.

Freeze Policies

 * Feature Freeze Policy (One week before Alpha Freeze)
 * Alpha Freeze Policy
 * String Freeze Policy (Same time as Alpha Freeze)
 * Final/Beta Freeze Policy

Who represents what to Fedora Release Engineering?
Various people attend rel-eng meetings and represent parts of Fedora engineering. If you wish to attend and represent a group of folks, just add your name below. Some representatives will also be releng members, but no representative needs to be.


 * WillWoods (QA)
 * JeremyKatz (Installer/Virt)
 * RexDieter (KDE)
 * JohnPoelstra (Features and scheduling)
 * JoshBoyer (PPC)
 * DimitrisGlezos (Localization)