Hi folks! I don't really have a lot for the agenda for the next
meeting - we have the Anaconda DNF Test Day coming up on Thursday, but
we have preparations for that in hand (if folks can be thinking about
ways to exercise DNF in anaconda that'd be great, any suggestions on
the trac ticket) and 22 Branch point and Alpha TC1 are scheduled for
Tuesday (we'll have to talk to releng about TC1 readiness).
If anyone has any topics to discuss, please reply to this mail and/or
just send a meeting announcement mail, otherwise we can take the hour
off and meet for the blocker review meeting at 17:00.
Another testing cycle is finally upon us, and it's about time we got
some Test Days scheduled for the F22 cycle. The Anaconda team has
already requested a test day  and there are several other changes
coming to F22 that could use some testing love - a full list can be
F22 also has several self-contained changes that could use some testing.
So my thought was, if there were things people would like to get tested,
but didn't think it warranted an entire day - then we could group these
together and run a test day to poke at several different things at the
same time. Thoughts on this?
For those of you not familiar with test days, a test day is an
online event aimed at testing a specific feature of an upcoming Fedora
Release. By utilizing IRC for organization/coordination and a Wiki
page for instructions and results, test days are easy to organize.
Anyone can request to host a test day or request that the QA team help
you out with the organization of the test day. A test day can be ran
for any feature or area of a distribution that focused testing would be
useful for. More information on test days can be found here:
To propose a test day, file a ticket on the QA Trac. A full
explanation can be found here:
https://fedoraproject.org/wiki/QA/Test_Days/Create . The SOP for
hosting a test day is here:
Traditionally test days have been held on Thursdays, but if you'd prefer
to have it on another day that's fine too. We're pretty flexible, but
having plenty of lead time helps to get the word out. Just put in your
ticket the date or time-frame you'd like, and we'll figure it out from
If you have any questions about test days or the process, please don't
hesitate to contact me or any other QA Team member in #fedora-qa on
Freenode or respond on the test list.
Thanks and happy testing!
# Fedora Quality Assurance Meeting
# Date: 2015-02-02
# Time: 16:00 UTC
# Location: #fedora-meeting on irc.freenode.net
It's QA meeting time again! If the folks working on it will be around
it'd be good to hear about the OpenQA work they've been doing. The
anaconda team would like to arrange an event to collaborate on
creating anaconda CI tests (Jenkins) from our release validation
tests, and we have some criteria proposals / changes we could run
If you have any other topic ideas, please reply to this mail and we'll
add them in the meeting! Thanks folks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Anaconda 'test day' planning
3. Release criteria / test case revisions
4. Open floor
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net