Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't
have anything urgent on the agenda, so let's take a well-earned break
after the F34 release!
If you're aware of anything important we have to discuss this week,
please do reply to this mail and we can go ahead and run the meeting.
IRC: adamw | Twitter: adamw_ha
Hi Fedora users, developers, and friends!
It's time to start thinking about Test Days for Fedora 35.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
You can see the schedule at
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.
If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*
And don't be afraid, there are a lot of more slots available for your
own Test Day!
[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on IRC. Thanks!
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
# Fedora Quality Assurance Meeting
# Date: 2021-04-26
# Time: 15:00 UTC
# Location: #fedora-meeting on irc.freenode.net
Fedora 34 is signed off, so let's do a final status check and make sure
everything's good to go, and check in on other items too.
If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 34 status and pre-release actions
3. Outstanding proposals
4. Test Day / community event status
5. Open floor
IRC: adamw | Twitter: adamw_ha
Since we anticipate a Fedora Linux 34 release candidate request today,
I am moving the Go/No-Go meeting from Thursday to Friday. This will
allow the QA team more time to perform validation tests.
The Fedora Linux 34 Final Go/No-Go meeting is scheduled for Friday
23 April at 1700 UTC in #fedora-meeting-1. At this time, we will
determine the status of F34 for the 27 April target date. For more
information about the Go/No-Go meeting, see the wiki.
He / Him / His
Senior Program Manager, Fedora & CentOS Stream