Fedora Program Management/ReadinessSOP

The Readiness meeting

Before each public release all of the groups participating the development of Fedora's next release meet to make sure the release is well coordinated. This meeting is called the: Release Readiness Meeting.

Responsibilities

FPGM key responsibility is to lead this important meeting.

Occurrence

This meeting is held for every public release - that means Alpha, Beta and Final but only once for each milestone.

SOP

• Invitation and reminder for the Readiness meeting for each milestone is sent on Mondays, as scheduled in schedule, to the devel-announce, test-announce and selected team mailing lists. Date, time and IRC meeting channel is communicated. Other ways of notifying key persons is welcomed (use Fedocal, other calendaring systems, direct pings etc.).
• The Go/No-Go meeting is held on Thursdays, 19:00 UTC.
• See IRC protocol for meeting hints
  • please #info statuses reported

Teams/individuals involved in this meeting:

• Ambassadors
• Design
• Documentation
• FESCo
• Fedora Engineering Manager
• Fedora Project Leader
• Marketing
• Infrastructure
• QA
• Release Engineering
• Translations
• Websites

IRC protocol

#startmeeting F[version] [milestone = Alpha, Beta, Final] Readiness Meeting
#meetingname f[version]-[milestone = alpha, beta, final]-readiness-meeting

#topic Roll Call

#chair [xxx]

#topic Purpose of this meeting
#info "Before each public release all of the groups participating the development of Fedora's next release meet to make sure the release is well coordinated."
#link https://fedoraproject.org/wiki/Release_Readiness_Meetings

#topic Current status
#topic Ambassadors
#topic Design
#topic Documentation
#topic FESCo
#topic Fedora Engineering Manager
#topic Fedora Project Leader
#topic Marketing
#topic Infrastructure
#topic QA
#topic Release Engineering
#topic Translations
#topic Open floor