ReleaseEngineering

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(How we do it: currently there are no meetings)
(Meeting Minutes: update meetbot url)
 
(17 intermediate revisions by 7 users not shown)
Line 12: Line 12:
  
 
* [[User:Ausil| Dennis Gilmore (dgilmore)]] (Leader)
 
* [[User:Ausil| Dennis Gilmore (dgilmore)]] (Leader)
* [[User:notting| Bill Nottingham (notting)]]
 
 
* [[User:kevin| Kevin Fenzi (nirik)]]
 
* [[User:kevin| Kevin Fenzi (nirik)]]
 +
* [[User:till| Till Mass (tyll)]]
 +
* [[User:parasense| Jon Disnard (masta)]]
 +
* [[User:sharkcz| Dan Horák (sharkcz)]] (secondary arches)
 +
* [[User:pbrobinson| Peter Robinson (pbrobinson)]]
 +
* [[User:pbabinca| Pavol Babincak (pbabinca)]]
 +
* [[User:maxamillion| Adam Miller (maxamillion)]]
  
 
Release Team members are approved by FESCo.  However, FESCo has
 
Release Team members are approved by FESCo.  However, FESCo has
Line 22: Line 27:
  
 
[[ReleaseEngineering/Overview|  Broad Overview]]  
 
[[ReleaseEngineering/Overview|  Broad Overview]]  
 +
 +
== Why we do things the way we do them ==
 +
 +
[[ReleaseEngineering/Philosophy|  Our philosophy]]
  
 
== Who's in Charge ==
 
== Who's in Charge ==
Line 30: Line 39:
 
== Things we Do ==
 
== Things we Do ==
  
* Set the schedule for releases including freeze dates, final release, slips, etc.
+
* Create official Fedora releases.
* Set blocker criteria for the release.
+
** Fedora Products
* Decide what packages go onto a spin.
+
*** Cloud
* Create official Fedora Spins.
+
*** Server
* Report progress towards release from Feature Freeze on.
+
*** Workstation
 +
** Fedora Spins  
 +
* Report progress towards release from [[Releases/Branched|Branched]] creation on.
 
* Give reports to FESCo on changes to processes.
 
* 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.
 
* 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
 
* Set policy on freeze management
 
* Administrate the build system(s)
 
* Administrate the build system(s)
 +
* Manage the packages git repositories (dist-git) and handle [[Package SCM admin requests]]
 +
* Remove unmaintained packages from Fedora
 +
* Push updated packages
 +
* write and maintain tools to compose and push Fedora
  
 
== Joining Release Engineering ==
 
== Joining Release Engineering ==
Line 44: Line 59:
 
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 [https://admin.fedoraproject.org/mailman/listinfo/rel-eng mailing list].
 
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 [https://admin.fedoraproject.org/mailman/listinfo/rel-eng 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) as the requests are submitted to trac or help with scripts for various rel-eng tasks.
+
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.
  
 
== How we do it ==
 
== How we do it ==
Line 53: Line 68:
  
 
=== Meetings ===
 
=== Meetings ===
There are currently no regular meetings.
+
rel-eng holds regular meetings every Monday at 14:30 UTC in #fedora-meeting-1 on the Freenode IRC network.
Previously meetings were regularly held every Friday at 1700 UTC.  Our meetings were 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
+
* [https://fedorahosted.org/rel-eng/report/10 Meeting agendas] are created from open tickets in Trac that contain the meeting keyword.
  
 
==== Meeting Minutes ====
 
==== Meeting Minutes ====
 +
Minutes are posted to the rel-eng mailing list. They are also available at the [http://meetbot.fedoraproject.org/sresults/?group_id=releng&type=team Meetbot team page for releng]
  
* http://fedoraproject.org/wiki/ReleaseEngineering/Meetings
+
There are also [[ReleaseEngineering/Meetings|historical Meeting Minutes for 2007-04-16 to 2009-05-04]].
  
 
== Current activities ==
 
== Current activities ==
Line 70: Line 85:
 
== Freeze Policies ==
 
== Freeze Policies ==
  
* [[ReleaseEngineering/FeatureFreezePolicy| Feature Freeze Policy]] (One week before Alpha Freeze)
+
* [[Milestone freezes|Milestone (Alpha, Beta, Final) freezes]]
* [[Alpha_Freeze_Policy|  Alpha Freeze Policy]]  
+
 
* [[ReleaseEngineering/StringFreezePolicy|  String Freeze Policy]] (Same time as Alpha Freeze)
 
* [[ReleaseEngineering/StringFreezePolicy|  String Freeze Policy]] (Same time as Alpha Freeze)
* [[ReleaseEngineering/FinalFreezePolicy| Final/Beta Freeze Policy]]
+
* [[Changes/Policy#Change freeze|Change freeze policy]] (that's 'Change' as in 'feature')
 +
* [[Updates Policy]] (not technically a freeze, but of interest)
  
 
== Who represents what to Fedora Release Engineering? ==
 
== 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.
+
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.
  
  
 
[[Category: Release Engineering]]
 
[[Category: Release Engineering]]

Latest revision as of 23:06, 29 July 2015

This page contains information about the Fedora Release Engineering team.

Contents

[edit] 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.

[edit] Composition

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, please read the section below.

[edit] What is Fedora Release Engineering?

Broad Overview

[edit] Why we do things the way we do them

Our philosophy

[edit] 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.

[edit] Things we Do

  • Create official Fedora releases.
    • Fedora Products
      • Cloud
      • Server
      • Workstation
    • Fedora Spins
  • 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)
  • Manage the packages git repositories (dist-git) and handle Package SCM admin requests
  • Remove unmaintained packages from Fedora
  • Push updated packages
  • write and maintain tools to compose and push Fedora

[edit] 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.

[edit] 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-releng or on the releng mailing list. For requests, please consult the contact information above.

[edit] Meetings

rel-eng holds regular meetings every Monday at 14:30 UTC in #fedora-meeting-1 on the Freenode IRC network.

  • Meeting agendas are created from open tickets in Trac that contain the meeting keyword.

[edit] Meeting Minutes

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.

[edit] Current activities

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

See Releases for information about Fedora releases, including schedules.

[edit] Freeze Policies

[edit] 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.