Another testing cycle is finally upon us, and it's about time we got some
Test Days scheduled/planned for the F30 cycle.
This cycle has major changes and could use some testing love - a full list can be found here:

http://fedoraproject.org/wiki/Releases/30/ChangeSet

F30 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:
https://fedoraproject.org/wiki/QA/Test_Days

To propose a test day, file an issue on Pagure[https://pagure.io/fedora-qa/issues] with F30 as Milestone.

A full explanation can be found here:
https://fedoraproject.org/wiki/QA/Test_Days/Create
The SOP for hosting a test day is here:
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management

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!

Thanks
//sumantro
freenode : sumantro