The Fedora 44 schedule is winding up, and it’s time we started thinking about what we’d want to have test days for. There are several changes accepted already for F44, and the window for proposals is still open so more may come. You can find the list of accepted Changes here.
Please take some time and look through the list and see if there’s anything you’d be interested in testing - or if there’s something you think should get some testing that isn’t in the change set!
For those of you not familiar with them, test days are online events aimed at testing a specific feature of an upcoming Fedora release. We organize the event in a ticket, provide a Wiki page with instructions, and have a page on the testdays webapp for reporting results. During the event, folks can compare notes and ask for help in the Matrix chat room. Anyone can request to host test days or request that the Quality team help you out with organizing. Test days can be run for any feature or area of a distribution that focused testing would be useful for. We use the name “test days” as it’s been around for a while, but many events run for more than a single day, now, to allow more time for folks to test. More information on test days can be found in the wiki.
To propose a test day, file a ticket on Pagure (for now).
You can look at existing issues with the test day tag to get an idea how the ticket can look; please include details on what topic you want to cover, and an idea of what dates you would like to hold it. You can also look at the SOP for hosting a test day.
If you have any questions about test days or the process, please don’t hesitate to contact me or any other Quality team member on Matrix or reply here.
Thanks and happy testing!
A closer look shows that there is some broken loop causing Changes to repeat multiple times. Any idea what a fix might be?