Fedora 21 Beta Go/No-Go Meeting, Thursday, October 30 @ 17:00 UTC
by Jaroslav Reznik
Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 21 Beta.
Thursday, October 30, 2014 17:00 UTC (1 PM EDT, 10 AM PDT, 18:00 CET)
Reminder: Europe already moved from summer time, winter is coming!
"Before each public release Development, QA and Release Engineering meet
to determine if the release criteria are met for a particular release.
This meeting is called the Go/No-Go Meeting."
"Verifying that the Release criteria are met is the responsibility of
the QA Team."
Release Candidate (RC) availability and good QA coverage are prerequisites
for the Go/No-Go decision.
For more details about this meeting see:
https://fedoraproject.org/wiki/Go_No_Go_Meeting
In the meantime, keep an eye on the Fedora 21 Beta Blocker list:
http://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist
You can help us with release validation, follow instructions at:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan
Jaroslav
9 years, 4 months
Fedora 21 Beta RC2 status is **FAILED**, RC3 will be coming
by Adam Williamson
Wanted to keep everyone in the loop so people don't feel like their time
has been wasted.
We discovered at the blocker review meeting today that there's a problem
with the RC2 compose. Blocker and FE packages that were pushed stable
yesterday - https://fedorahosted.org/rel-eng/ticket/5988#comment:17 -
were taken out of the 'bleed' repository where blocker/FE fixes are
pulled into composes before they go stable, but they did not actually
get mashed/distributed in time to be included in the RC2 compose.
The upshot is that RC2 has incorrect (old) versions of initscripts,
systemd and fedup-dracut. This means that RC2 will be subject to at
least https://bugzilla.redhat.com/show_bug.cgi?id=1114786 ,
https://bugzilla.redhat.com/show_bug.cgi?id=1099299 and
https://bugzilla.redhat.com/show_bug.cgi?id=1146580 , so it definitely
cannot be released as the Beta. We will need an RC3 compose, and testing
of RC2 will not be sufficient to clear RC3 for release due to the
significance of systemd.
Testing of RC2 is not entirely useless - it's still useful to check
there are no regressions in anaconda 21.48-13, for instance - but we
will need to do a good degree of testing on RC3 when it lands later
today before we can consider clearing RC3 for release. I'm very sorry to
folks who've already put work into testing RC2 for the mistake. Keep
your eyes peeled for RC3!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 4 months
2014-10-27 @ 15:00 UTC - Fedora QA Meeting
by Adam Williamson
# Fedora Quality Assurance Meeting
# Date: 2014-10-27
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
It's meeting time again tomorrow! Right now I only have one topic for
the agenda, but it's a biggy - let's make sure everyone's pointed in the
same direction for 21 Beta validation. Many thanks to everyone who
helped out so much with the validation efforts last week - it wasn't for
lack of effort on our part that the slip was necessary! I'm hoping we'll
be able to roll an RC2 on Monday and ideally that, or if we find any
other issues an RC3 on Tuesday, will be shippable and no more validation
heroics will be required!
== Proposed Agenda Topics ==
1. Fedora 21 Beta status
2. Open floor
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
9 years, 4 months