From Fedora Project Wiki

m (added the page to release criteria category)
mNo edit summary
Line 2: Line 2:


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:
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_29_Beta_Release_Criteria | Beta]]  
* [[Fedora_24_Beta_Release_Criteria | Beta]]  
* [[Fedora_29_Final_Release_Criteria | Final]]  
* [[Fedora_24_Final_Release_Criteria | Final]]  


== Meeting Organization ==
== 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].
* 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 is held on IRC on <code>#fedora-meeting-1</code>


== Meeting Outcomes ==
== Meeting Outcomes ==

Revision as of 19:29, 4 September 2018

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-1

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.