From Fedora Project Wiki

m (Update releng branch name)
 
(60 intermediate revisions by 21 users not shown)
Line 1: Line 1:
= Fedora Release Engineering Team =
{{autolang|base=yes}}


The [https://docs.pagure.org/releng/ Fedora Release Engineering documentation] is maintained in [https://pagure.io/releng/blob/main/f/docs pagure].


 
[[Category: Release Engineering]]
== Composition ==
 
* JesseKeating (f13)
* JoshBoyer (jwb)
* BillNottingham (notting)
* JeremyKatz (jeremy)
* RexDieter (rdieter)
* WarrenTogami (warren)
* WillWoods (wwoods)
* TomCallaway (spot)
* LukeMacken (lmacken)
* JohnPoelstra (poelcat)
 
 
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 rel-eng@fedoraproject.org.
 
== 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)
 
See our [[ReleaseEngineering/SOP|  Standard Operating Procedures]]  for details on how we do the things we do.
 
See our [[ReleaseEngineering/Projects|  Projects Page]]  for information on our current projects.
 
== Where we do it ==
 
* IRC: #fedora-devel
* Mailing List: rel-eng@fedoraproject.org (just an alias right now, no list yet)
 
Most discussions regarding release engineering will happen either in #fedora-devel or on the fedora-devel-list mailing list.  Requests for the rel-eng team to do something should be sent to rel-eng@fedoraproject.org.
 
=== 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 ====
 
* http://fedoraproject.org/wiki/ReleaseEngineering/Meetings
 
== 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)
 
----
[[Category:Fedora]]

Latest revision as of 04:35, 10 October 2021