# F19 Beta Blocker Review meeting #1
# Date: 2013-04-24
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

The first blocker review meeting for F19 Beta will be held tomorrow.
Should be a short one, just a few proposed blockers so far.

We'll be running through the Beta blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/milestone/19/beta/buglist" title="http://qa.fedoraproject.org/blockerbugs/milestone/19/beta/buglist">http://qa.fedoraproject.org/blockerbugs/milestone/19/beta/buglist</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the Beta release criteria [1] and should stay
on the list
2.

Hi, folks. It's that time again: Graphics Test Week! Tomorrow
(2013-04-23) is Intel Test Day, Wednesday 2013-04-24 is Nouveau Test
Day, and Thursday 2013-04-25 is Radeon Test Day:

<a href="https://fedoraproject.org/wiki/Test_Day:2013-04-23_Intel" title="https://fedoraproject.org/wiki/Test_Day:2013-04-23_Intel">https://fedoraproject.org/wiki/Test_Day:2013-04-23_Intel</a>
<a href="https://fedoraproject.org/wiki/Test_Day:2013-04-24_Nouveau" title="https://fedoraproject.org/wiki/Test_Day:2013-04-24_Nouveau">https://fedoraproject.org/wiki/Test_Day:2013-04-24_Nouveau</a>
<a href="https://fedoraproject.org/wiki/Test_Day:2013-04-25_Radeon" title="https://fedoraproject.org/wiki/Test_Day:2013-04-25_Radeon">https://fedoraproject.org/wiki/Test_Day:2013-04-25_Radeon</a>

This is one of those events where we really need as much data as
possible - the idea is just to get testing on as wide a range of
hardware as we can manage. So please, if you have a few spare minutes,
come out and test! It's very easy.

# Fedora Quality Assurance Meeting
# Date: 2013-04-22
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again today/tomorrow! We signed off on Alpha this week
(yay!), so it's time for some Beta prep.

This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
<a href="https://fedoraproject.org/wiki/QA/Meetings/20130422" title="https://fedoraproject.org/wiki/QA/Meetings/20130422">https://fedoraproject.org/wiki/QA/Meetings/20130422</a>
The current proposed agenda is included below.

== Proposed Agenda Topics ==
1. Previous meeting follow-up
2.

Hi folks!

So, good news: following the blocker review meeting this morning, we're
looking quite close to signing off on Alpha. We just need to fill out
the RC4 test matrices before tomorrow's go/no-go meeting, and hope we
don't find any more blocker bugs.

Hi folks - thanks for helping out with the last UEFI testing request, it
was very helpful. If we could impose again, it would be really helpful
if anyone with a UEFI-capable system could try a UEFI native install of
Alpha RC3:

<a href="https://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC3/" title="https://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC3/">https://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC3/</a>

and report your results. We are hopeful that the major bugs that
affected previous builds are resolved, and many or most UEFI installs
should succeed at this point. If you try, please report whether you got
a successful installation, and if not, what problem you ran into.

# F19 Alpha Blocker Review meeting #7
# Date: 2013-04-15
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

Again, we'll be having a blocker review meeting to follow up the QA
meeting on Monday. Only a few bugs to look at, should be a quick one.

We'll be running through the alpha blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the Alpha release criteria [1] and should stay
on the list
2.

# Fedora Quality Assurance Meeting
# Date: 2013-04-15
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again today/tomorrow! Once again, F19 Alpha is the
main topic: unfortunately we missed last week, but things look good for
this week.

This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
<a href="https://fedoraproject.org/wiki/QA/Meetings/20130415" title="https://fedoraproject.org/wiki/QA/Meetings/20130415">https://fedoraproject.org/wiki/QA/Meetings/20130415</a>
The current proposed agenda is included below.

== Proposed Agenda Topics ==
1.

Hi, folks. This is a special testing request for F19 Alpha.

There are known to be a couple of bugs that can cause UEFI installation
to fail because there isn't enough space in the firmware NVRAM; as a fix
for that somewhat-infamous bricking bug on some laptops, the current F19
kernel refuses to write to the NVRAM if it's 50% or more full. As Josh
put it:

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=947142" title="https://bugzilla.redhat.com/show_bug.cgi?id=947142">https://bugzilla.redhat.com/show_bug.cgi?id=947142</a>

"The kernel now limits efivars from using more than 50% of the available
firmware space.

Hi folks! Time for the first blocker status mail of the Fedora 19 cycle.

# F19 Alpha Blocker Review meeting #4
# Date: 2013-04-08
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

As we agreed in discussing modifications to the blocker review process,
it's a better idea to have an official blocker review meeting right
after the QA meeting on Mondays than to do blocker review during the QA
meeting - so let's do that! A few blockers are on the proposed list and
it'd help to deal with them so we know where we stand as regards RC1.

# Fedora Quality Assurance Meeting
# Date: 2013-04-08
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again today/tomorrow! We'll be focusing in on Fedora
19 Alpha status - looks like we have a chance to make the release date.

This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
<a href="https://fedoraproject.org/wiki/QA/Meetings/20130408" title="https://fedoraproject.org/wiki/QA/Meetings/20130408">https://fedoraproject.org/wiki/QA/Meetings/20130408</a>
The current proposed agenda is included below.

== Proposed Agenda Topics ==
1.

Hey folks! Yes, it's Test Day time yet again: tomorrow (2013-04-04) is
Printing Test Day over in #fedora-test-day. It's a nice easy Test Day to
get involved in - the testing isn't difficult and can be done from a
live image, and we pretty much all still have printers. Do drop by and
help out if you can. All test instructions and other details are on the
Wiki page:

<a href="https://fedoraproject.org/wiki/Test_Day:2013-04-04_Printing" title="https://fedoraproject.org/wiki/Test_Day:2013-04-04_Printing">https://fedoraproject.org/wiki/Test_Day:2013-04-04_Printing</a>

Hope to see you there!

It's Test Day time again today, folks. Sorry for the short notice -
looks like everyone was expecting someone else to send the announcement
mail...

Today - 2013-04-02 - is OpenStack Test Day:
<a href="https://fedoraproject.org/wiki/Test_Day:2013-04-02_OpenStack" title="https://fedoraproject.org/wiki/Test_Day:2013-04-02_OpenStack">https://fedoraproject.org/wiki/Test_Day:2013-04-02_OpenStack</a>

Please do come out and help us test the integration of OpenStack into
Fedora 19! All the testing instructions are on the wiki, and there are
people standing by in #fedora-test-day to help with testing and discuss
results.

# Fedora Quality Assurance Meeting
# Date: 2013-04-01
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again on Monday! It's officially a holiday in Canada
and I just rolled in from a barbeque, so there's about a 50/50 chance of
me showing up. But don't let that stop you!

This is a reminder of the upcoming QA meeting.

# F19 Alpha Blocker Review meeting #2
# Date: 2013-03-27
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net

It's that time again - blocker review meeting time!

We'll be running through the alpha blockers and freeze exception bugs.
The current list is available at:
<a href="http://qa.fedoraproject.org/blockerbugs/current" title="http://qa.fedoraproject.org/blockerbugs/current">http://qa.fedoraproject.org/blockerbugs/current</a>

We'll be reviewing the bugs to determine ...

1. Whether they meet the alpha release criteria [1] and should stay
on the list
2.

# Fedora Quality Assurance Meeting
# Date: 2013-03-25
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again on Monday! We're rolling on F19 testing now, so
let's check where we stand on TC1 testing after the weekend (please test
over the weekend, folks!) and plan for TC2 / RC1. We should also look at
how the big showstopper in yum for network installs is affecting our
test coverage and try to mitigate that.

The Fedora 19 GNOME Test Day is just now kicking off!

<a href="https://fedoraproject.org/wiki/Test_Day:2013-03-21_Gnome_3.8" title="https://fedoraproject.org/wiki/Test_Day:2013-03-21_Gnome_3.8">https://fedoraproject.org/wiki/Test_Day:2013-03-21_Gnome_3.8</a>

Come join the fun in #fedora-test-day on Freenode IRC. There are live
images and full test instructions available on the wiki page (just
x86_64 for now, i686 is being built). Help us ensure GNOME 3.8 is
polished for Fedora 19 and other distributions!

# Fedora Quality Assurance Meeting
# Date: 2013-03-18
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again tomorrow / today! We should be doing Alpha TC1
this week, so we need to look at the status of current F19 and see what
needs to be done to make that happen. We can discuss my criteria
revision proposal further, and follow up on last week's KDE Test Day and
make plans for this week's GNOME Test Day.

This is a reminder of the upcoming QA meeting.

So I installed fedora-release from the F19 repo and did a yum
distro-sync today. Then I installed a new kernel build. Then I rebooted.

Then nothing would boot at all.

It turns out this is because the release name of Fedora 19 is:

Schrödinger's Cat

with a single quote used as an apostrophe. That release name gets
written into the grub entry for a kernel when you're installing it.

# Fedora Quality Assurance Meeting
# Date: 2013-03-11
# Time: 15:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again tomorrow / today! Please note the time: as
clocks went forward in most places today, the meeting will now be at
15:00 UTC.

It occurred to me that it's just possible someone might find this
interesting but not be subscribed to test@, so I thought I'd mention it
here.

We have recently created the new list 'qa-devel at
lists.fedoraproject.org' for discussion of QA tool development. It will
subsume the autoqa-devel list, but it also covers other tools being
developed by and mostly for the QA team, including the blocker bug
webapp and the blocker bug submission tool. So...if it interests
you...check it out :)

# Fedora Quality Assurance Meeting
# Date: 2013-03-04
# Time: 16:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again very soon. Crap on a stick, so soon. Note to
self: Angry Birds is not a good choice of app with which to 'test your
tablet'. Especially not the night before a meeting. For three hours solid.

This is a reminder of the upcoming QA meeting.

# Fedora Quality Assurance Meeting
# Date: 2013-02-25
# Time: 16:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again tomorrow. We have the blocker process and
automatic blocker stuff from this week in the follow-up section, and a
couple of other things to go over.

This is a reminder of the upcoming QA meeting.

We discussed a few possible changes to the blocker bug meeting process
at the QA meeting this week. It was agreed that I'd draft up these
changes for list discussion. So here they are!

# Fedora Quality Assurance Meeting
# Date: 2013-02-18
# Time: 16:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again tomorrow. Topic list is pretty short this week,
so might be a short meeting. Please add anything I forgot.

This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
<a href="https://fedoraproject.org/wiki/QA/Meetings/20130218" title="https://fedoraproject.org/wiki/QA/Meetings/20130218">https://fedoraproject.org/wiki/QA/Meetings/20130218</a>

The current proposed agenda is included below.

== Proposed Agenda Topics ==
1. Blocker review process
2.

# Fedora Quality Assurance Meeting
# Date: 2013-02-11
# Time: 16:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again tomorrow. I'll be out for the day, so if someone
else could run the meeting, that'd be great. Note: I'm happy to set up
the Test Day cycle if no-one else takes it, and tflink may be able to
talk a bit about what we were discussing with regards to the criteria
revision task this week.

This is a reminder of the upcoming QA meeting.

# Fedora Quality Assurance Meeting
# Date: 2013-02-04
# Time: 16:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again tomorrow. This week we'll be covering stuff we
didn't get around to last week, mostly.

This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
<a href="https://fedoraproject.org/wiki/QA/Meetings/20130204" title="https://fedoraproject.org/wiki/QA/Meetings/20130204">https://fedoraproject.org/wiki/QA/Meetings/20130204</a>

The current proposed agenda is included below.

== Proposed Agenda Topics ==
1. Criteria Revision
2. Test Case Revision
3.

# Fedora Quality Assurance Meeting
# Date: 2013-01-28
# Time: 16:00 UTC
(<a href="https://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="https://fedoraproject.org/wiki/Infrastructure/UTCHowto">https://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

It's meeting time again tomorrow. F18 is done, and it's time to try and
set up plans for the F19 cycle. I've tried to cover the most
interesting / pressing topics - please add any I've forgotten!

This is a reminder of the upcoming QA meeting.

Hey folks!

At FUDCon Lawrence, Tim Flink presented on the Fedora blocker bug and
'NTH' processes, and we got some interesting and useful feedback. People
felt that the 'nice to have' / 'accepted' name used in that process was
confusing and difficult to understand, and that the aliases used for the
tracker bugs were inconsistent.

We developed a proposal to rename the aliases and the 'nice to have'
process.

Sorry for the earlier incomplete version of this mail, sent in error.
Damn ctrl-combinations.

Hey folks! So we are definitely on the final night of Fedora 18 testing
now (everyone, take a drink).

As it's Fedora, we came up with a fudge at the go/no-go meeting today:
we agreed we're definitely shipping either RC3 or RC4. RC3 is RC2 with
the final release notes, and RC4 is RC3 with the fprintd fix for
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=810040" title="https://bugzilla.redhat.com/show_bug.cgi?id=810040">https://bugzilla.redhat.com/show_bug.cgi?id=810040</a> .