Release Readiness

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-27	Ready
Localization	Jean-Baptsite	2020-02-26	Not ready	We need docs i18n automation working to allow localization of release notes (https://pagure.io/fedora-infrastructure/issue/8691) we need release notes available for translation one week before release (no issue yet, only formal confirmation new process with Weblate really works should be sufficient. Note: this is an improvement compare to previous releases) We need to have Websites content one week before release (no issue yet, only formal confirmation new process with Weblate really works should be sufficient. Note: this is an improvement compare to previous releases)
Infrastructure	Kevin Fenzi	2020-02-27	Not ready	Need someone to work on i18n process above. :) Need bits to mirror, etc. Otherwise ready
QA	Frantisek Zatloukal	2020-03-05	Not ready	There are unfixed blocker bugs in Fedora 32: https://qa.fedoraproject.org/blockerbugs/milestone/32/beta/buglist There is no Beta candidate compose Validation Testing hasn't been completed (no candidate image available yet) (adamwill) We are not clear on the status and expectations in regard to the IoT edition: see qa#623, qa#618, iot#24

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