From Fedora Project Wiki

m (Contact Information: typo)
(Undo revision 448522 by Petersen (talk))
(50 intermediate revisions by 17 users not shown)
Line 1: Line 1:
This page contains information about the Fedora Release Engineering team.
== Contact Information ==
The [ Fedora Release Engineering documentation] is maintained in [ pagure].
* IRC: #fedora-devel
* Mailing List: [ rel-eng@'''lists.'''] (just an alias right now, no list yet)
* Issue tracker:
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.
[[Category: Release Engineering]]
{{Template:Caution}} The old e-mail address <s></s> (note the missing lists.) does not work currently.
== Composition ==
* [[User:f13| Jesse Keating (f13)]] (Leader)
* [[User:notting| Bill Nottingham (notting)]]
* [[User:jeremy| Jeremy Katz (jeremy)]]
* [[User:poelstra| John Poelstra (poelcat)]]
* [[User:jwb| Josh Boyer (jwb)]]
* [[User:lmacken| Luke Macken (lmacken)]]
* [[User:rdieter| Rex Dieter (rdieter)]]
* [[User:spot| Tom Callaway (spot)]]
* [[User:warren| Warren Togami (warren)]]
* [[User:wwoods| Will Woods (wwoods)]]
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| contact information above]].
== What is Fedora Release Engineering? ==
[[ReleaseEngineering/Overview|  Broad Overview]]
== Who's in Charge ==
JesseKeating.  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)
== How we do it ==
See our [[ReleaseEngineering/SOP|  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| contact information above]].
=== Meetings ===
Meetings are regularly held every Monday at 1800 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.
* [[ReleaseEngineering/Meetings/Agenda|  Proposed Agenda]]
==== Meeting Minutes ====
== Current activities ==
See our [[ReleaseEngineering/Projects|  Projects Page]] for information on our current projects.
See [[Releases]] for information about Fedora releases, including schedules.
== Freeze Policies ==
* [[ReleaseEngineering/TestFreezePolicy|  Test Freeze Policy]]
* [[ReleaseEngineering/FeatureFreezePolicy|  Feature Freeze Policy]]
* [[ReleaseEngineering/DevelFreezePolicy|  Devel Freeze Policy]]
* [[ReleaseEngineering/FinalFreezePolicy|  Final Freeze Policy]]
* [[ReleaseEngineering/StringFreezePolicy|  String 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, scheduling, and meeting minutes)
* JoshBoyer (PPC)
* DimitrisGlezos ([[L10N|Localization]])

Latest revision as of 08:45, 31 May 2016

The Fedora Release Engineering documentation is maintained in pagure.