The compose that we decided yesterday to wait for failed, as has a
subsequent compose attempt. Because there's no material change in
status from yesterday's go/no-go meeting and we will not have a
successful compose in place by the time of today's meeting, there is
no value in repeating the Go/No-Go meeting today.
We will consider Fedora 30 Beta No-Go and move to the Beta target date
#1 (2019-04-02). The next Fedora 30 Beta Go/No-Go meeting will be
Thursday, 28 March at 1700 UTC in #fedora-meeting-1.
https://apps.fedoraproject.org/calendar/Fedora%20release/2019/3/28/#m9491
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
Pronouns: he/him
In the Fedora 30 Beta Go/No-Go meeting we decided to delay the
decision by 1 day. This will allow the creation of a new compose (in
progress) that fixes the one outstanding blocker bug. We determined
that the nature of this fix would not require the full test suite and
that delaying the decision by one day in anticipation of success was
preferable to a full week delay.
Please join us at 1700 UTC on Friday, 22 March in #fedora-meeting-1
for another Go/No-Go meeting:
https://apps.fedoraproject.org/calendar/Fedora%20release/2019/3/22/#m9493
As a reminder, we will be holding the Release Readiness meeting
shortly. It will be at 1900 UTC today in #fedora-meeting-1:
https://apps.fedoraproject.org/calendar/meeting/9492/?from_date=2019-03-18
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
Pronouns: he/him
Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 30
Beta Release Readiness meeting. This meeting will be held on Thursday,
2018-03-21 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the Beta
release of Fedora 30. Please note that this meeting will be held even
if the release is delayed at the Go/No-Go meeting on the same day two
hours earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/Fedora%20release/2019/3/21/#m9492
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis