{{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source hosted along side the code in the [https://pagure.io/releng releng pagure repository]}}

This page contains information about the Fedora Release Engineering team.

This page contains information about the Fedora Release Engineering team.

Contact Information

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.

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 trac or help with scripts for various rel-eng tasks.

Freeze Policies

Who represents what to Fedora Release Engineering?

Various people attend rel-eng meetings and represent different 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.