The release status of Fedora 32 Beta is no-go.
Due to an open previous release blocker and insufficient test
coverage, Fedora 32 Beta was declared "no-go". We will reconvene at
1800 UTC (note the departure from the usual time) on Friday, 13
March[1] to re-evaluate the existing release candidate.
If we determine at that time that it is go, we will release Fedora 32
Beta on the preferred target date of 17 March. If we determine at that
time it is no-go, or if an obvious no-go condition arises prior to the
meeting, we will reconvene on 19 March to target a release date of 24
March.
For more information, please see the minutes[2] from the Fedora 32
Beta Go/No-Go meeting.
[1] https://apps.fedoraproject.org/calendar/Fedora%20release/2020/3/13/#m9730
[2] https://meetbot.fedoraproject.org/fedora-meeting-1/2020-03-12/f32-beta-go_n…
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
Dear all,
The Go/No-Go meeting for the Fedora 32 Beta release will be held on
Thursday, 2020-03-12 at 17:00 UTC in #fedora-meeting-1. For more
information, see: https://fedoraproject.org/wiki/Go_No_Go_Meeting
View the meeting on Fedocal at:
https://apps.fedoraproject.org/calendar/meeting/9716/
As usual, we will have the Release Readiness meeting following at
19:00 UTC. This time, I'm asking teams to do their homework in
advance. Please update your team's status at:
https://fedoraproject.org/wiki/Release_Readiness
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
If you're subscribed to this list and you don't want to see traffic
related to the release readiness process (below), now is a good time
to unsubscribe.
(Posting to many mailing lists for visibility. I apologize if you see
this more times than you'd like.)
You may have already seen my Community Blog post[1] about changing the
Release Readiness meeting process. The meeting has questionable value
in the current state, so I want to make it more useful. We'll do this
by having teams self-report readiness issues on a dedicated wiki
page[2] beginning now. This gives the community time to chip in and
help with areas that need help without waiting until days before the
release.
I invite teams to identify a representative to keep the wiki page up
to date. Update it as your status changes and I'll post help requests
in my weekly CommBlog posts[3] and the FPgM office hours[4] IRC
meeting. The Release Readiness meeting will be shortened to one hour
and will review open concerns instead of polling for teams that may or
may not be there. We will use the logistics mailing list[5] to discuss
issues and make announcements, so I encourage representatives to join
this list.
[1] https://communityblog.fedoraproject.org/fedora-program-update-2020-08/
[2] https://fedoraproject.org/wiki/Release_Readiness
[3] https://communityblog.fedoraproject.org/category/program-management/
[4] https://apps.fedoraproject.org/calendar/council/#m9570
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
