From Fedora Project Wiki

m (Add F32 beta docs status)
 
(11 intermediate revisions by 3 users not shown)
Line 7: Line 7:
== Current Status ==
== Current Status ==


'''Target release:''' Fedora 32 Beta
'''Target release:''' Fedora 33 Final


{| class="wikitable"
{| class="wikitable"
Line 13: Line 13:
! Team !! Representative !! Last updated !! Status !! Notes
! Team !! Representative !! Last updated !! Status !! Notes
|-
|-
| Program Management || [[User:Bcotton|bcotton]] || 2020-02-27 || Ready ||  
| Program Management || [[User:Bcotton|bcotton]] || 2020-10-08 || Ready ||  
|-
|-
| Localization || [[User:jibecfed|Jean-Baptsite]] || 2020-02-26 || Not ready
| Localization || [[User:jibecfed|Jean-Baptsite]] || ||  
||
||
* 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 || [[User:Kevin|Kevin Fenzi]] || 2020-02-27 || Not ready
| Infrastructure || [[User:Kevin|Kevin Fenzi]] || 2020-09-23 || Ready
||
||
* Need someone to work on i18n process above. :)
* Need bits to mirror, etc. Otherwise ready
|-
|-
| QA || [[User:Frantisekz|Frantisek Zatloukal]] || 2020-03-11 || Not ready
| QA || [[User:Frantisekz|Frantisek Zatloukal]] || ||
||
|| https://qa.fedoraproject.org/blockerbugs/milestone/33/final/buglist
* Beta candidate compose complete
|-
* Validation Testing hasn't been completed yet
| RelEng || [[User:mohanboddu|Mohan Boddu]] || 2020-09-23 || Ready || RC1.3 is composed and being tested
* (adamwill) We are not clear on the status and expectations in regard to the IoT edition: see [https://pagure.io/fedora-qa/issue/623 qa#623], [https://pagure.io/fedora-qa/issue/618 qa#618], [https://pagure.io/fedora-iot/issue/24 iot#24]
|-
| Documentation || [[User:pbokoc|Petr Bokoc]] ||  ||  ||
|-
| Fedora Magazine || [[User:bcotton|Ben Cotton]] || 2020-10-08 || Not ready || mattdm is preparing the release announcement post
|-
|-
| Documentation || [[User:pbokoc|Petr Bokoc]] || 2020-03-12 || Ready || Docs doesn't have any beta deliverables. We need to branch versioned docs for f32 but that'll be done shortly.
| Websites || [[User:bcotton|Ben Cotton]] || 2020-10-07 || Not ready || IoT assets updated. Just need to prepare the Final Release pieces
|}
|}



Latest revision as of 15:02, 14 October 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 33 Final

Team Representative Last updated Status Notes
Program Management bcotton 2020-10-08 Ready
Localization Jean-Baptsite
Infrastructure Kevin Fenzi 2020-09-23 Ready
QA Frantisek Zatloukal https://qa.fedoraproject.org/blockerbugs/milestone/33/final/buglist
RelEng Mohan Boddu 2020-09-23 Ready RC1.3 is composed and being tested
Documentation Petr Bokoc
Fedora Magazine Ben Cotton 2020-10-08 Not ready mattdm is preparing the release announcement post
Websites Ben Cotton 2020-10-07 Not ready IoT assets updated. Just need to prepare the Final Release pieces

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