From Fedora Project Wiki

(Created page with 'This is a stub for a page to explain the ''Release Readiness Meetings'' that happen with all of the teams in Fedora prior to release. ~~~~')
 
m (added the page to release criteria category)
(6 intermediate revisions by 5 users not shown)
Line 1: Line 1:
This is a stub for a  page to explain the ''Release Readiness Meetings'' that happen with all of the teams in Fedora prior to release.
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.


[[User:Poelstra|poelcat]] 16:24, 2 December 2009 (UTC)
This meeting is called the: ''Release Readiness Meeting''.  The Release Readiness Meeting is held after after the [[ Engineering_Readiness_Meetings| ''Go/No-Go Meeting'']] that is held for each public release:
* [[Fedora_24_Alpha_Release_Criteria | Alpha]]  
* [[Fedora_24_Beta_Release_Criteria  | Beta]]
* [[Fedora_24_Final_Release_Criteria | Final]]
 
== Meeting Organization ==
* The meeting facilitator sends an email announcement five days before the meeting, specifying the meeting location and time to [https://lists.fedoraproject.org/archives/list/logistics@lists.fedoraproject.org/ Logistics List].
* Meeting is held on IRC on <code>#fedora-meeting</code>
 
== Meeting Outcomes ==
# Status from each team
# Confirmation from each team that they are prepared for release day or will be ready on that day.
 
== Contingency Plan ==
* Delay the release.
 
[[Category:Release Criteria]]

Revision as of 22:57, 19 May 2016

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. The Release Readiness Meeting is held after after the Go/No-Go Meeting that is held for each public release:

Meeting Organization

  • The meeting facilitator sends an email announcement five days before the meeting, specifying the meeting location and time to Logistics List.
  • Meeting is held on IRC on #fedora-meeting

Meeting Outcomes

  1. Status from each team
  2. Confirmation from each team that they are prepared for release day or will be ready on that day.

Contingency Plan

  • Delay the release.