From Fedora Project Wiki

(Initial readiness page)
 
(Adding RelEng)
(12 intermediate revisions by 6 users not shown)
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 ==


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


{| class="wikitable"
{| class="wikitable"
Line 11: Line 13:
! Team !! Representative !! Last updated !! Status !! Notes
! Team !! Representative !! Last updated !! Status !! Notes
|-
|-
| Program Management || [[User:Bcotton|bcotton]] || 2020-02-05 || Not ready || Need to publish the new release readiness process
| Program Management || [[User:Bcotton|bcotton]] || 2020-02-27 || Ready ||
|-
| Localization || [[User:jibecfed|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 || [[User:Kevin|Kevin Fenzi]] || 2020-03-17 || ready
||
|-
| QA || [[User:Frantisekz|Frantisek Zatloukal]] || 2020-03-11 || Not ready
||
* Beta candidate compose complete
* Validation Testing hasn't been completed yet
* (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]
|-
| RelEng || [[User:mohanboddu|Mohan Boddu]] || 2020-04-16 || Not ready
||
* We need another RC to fix the outstanding blockers
|-
| 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.
|-
| Fedora Magazine || [[User:bcotton|Ben Cotton]] || 2020-04-16 || Not ready || Announcement draft is in mattdm's hands. Needs an image created.
|}
|}


Revision as of 19:17, 16 April 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 Final

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-03-17 ready
QA Frantisek Zatloukal 2020-03-11 Not ready
  • Beta candidate compose complete
  • Validation Testing hasn't been completed yet
  • (adamwill) We are not clear on the status and expectations in regard to the IoT edition: see qa#623, qa#618, iot#24
RelEng Mohan Boddu 2020-04-16 Not ready
  • We need another RC to fix the outstanding blockers
Documentation 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.
Fedora Magazine Ben Cotton 2020-04-16 Not ready Announcement draft is in mattdm's hands. Needs an image created.

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
Retrieved from "https://fedoraproject.org/w/index.php?title=Release_Readiness&oldid=572768"