Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't
see anything particularly urgent to discuss, so let's take the time
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.
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
First of all, thanks for spending some time and contributing to Fedora 28 Test Days.
This was by far the *most-engaging* testday season with 11 Test Days and 201 Testers executing 925 Test cases.
Last Flock, we approched the Kernel folks to run a test day with for every new kernel rebase and we are happy to
say, we get it tested throughly!
Most particpated Fedora 28 Test Days:
Test Day:2017-11-30 Kernel 4.14 Test Day
Testers: 49, Tests: 57
Test Day:2018-02-22 Kernel 4.15 Test Day
Testers: 42, Tests: 64
Test Day:2018-04-13 Kernel 4.16 Test Day
Testers: 32, Tests: 41
Test Day:2018-04-19 Upgrade Test Day
Testers: 60, Tests: 103
For every release we have:
1. Gnome Test Day
2. I18n Test Day
3. Cloud Test Day
4. Kernel Test Day
5. Upgrade Test Day
We want to increase this list with coming releases by adding more of release-blocking and mostly-used features/apps/changes apart from changeset of the
Thoughts that echoed throughout the F28 test day cycle:
1.Test days to run as async event (not bound to any release)
2.All Test days to kick off as soon as change sets are final(for changesets)
3.Test Day images needs to be squeezed to as minimal as possible
4.Try to set the test-cases and posts well in advance. There are many who post it for regional communities and an
annoucement well in advance helps them.
Another testing cycle is finally upon us, and it's about time we got some
Test Days scheduled/planned for the F29 cycle.
This cycle has major changes and could use some testing love - a full list can be found here:
F29 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.
For those of you not familiar with test days,
a test day is an online event aimed at testing a specific a 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 run 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 an issue on Pagure[https://pagure.io/fedora-qa/issues] with F29 as Milestone.
A full explanation can be found here:
The SOP for hosting a test day is here:
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!
freenode : sumantro