From Fedora Project Wiki

(Initial readiness page)
 
Line 2: Line 2:
  
 
This page is an asynchronous place for teams in Fedora to report their readiness for release. The idea is to address non-ready areas before the [[Release_Readiness_Meetings|Release Readiness meeting]]. Team representatives are encouraged to self-add. The Fedora Program Manager will reset this page before each release and send email reminders to the people listed.
 
This page is an asynchronous place for teams in Fedora to report their readiness for release. The idea is to address non-ready areas before the [[Release_Readiness_Meetings|Release Readiness meeting]]. Team representatives are encouraged to self-add. The Fedora Program Manager will reset this page before each release and send email reminders to the people listed.
 +
 +
If you list yourself as a contact, you should add yourself to the [https://lists.fedoraproject.org/archives/list/logistics@lists.fedoraproject.org/ logistics mailing list].
  
 
== Current Status ==
 
== Current Status ==

Revision as of 19:18, 24 February 2020

Release Readiness Status

This page is an asynchronous place for teams in Fedora to report their readiness for release. The idea is to address non-ready areas before the Release Readiness meeting. Team representatives are encouraged to self-add. The Fedora Program Manager will reset this page before each release and send email reminders to the people listed.

If you list yourself as a contact, you should add yourself to the logistics mailing list.

Current Status

Target release: Fedora 32 Beta

Team Representative Last updated Status Notes
Program Management bcotton 2020-02-05 Not ready Need to publish the new release readiness process

Example

Team Representative Last updated Status Notes
Websites Example User 2020-02-25 Ready Website ready for new JSON data
Marketing Otherexample User 2020-02-21 Not ready Need help generating talking points