test-announce November 2021

test-announce@lists.fedoraproject.org

5 participants
15 discussions

[Fedora 36] Call for Test Days
by Sumantro Mukherjee 09 Nov '21

09 Nov '21

Hi Fedora users, developers, and friends! It's time to start thinking about Test Days for Fedora 36. 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 https://fedoraproject.org/wiki/QA/Test_Days . 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 https://fedoraproject.org/wiki/QA/SOP_Test_Day_management . You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days . 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 Test Days: 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 cycle. 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! -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

Fedora-IoT 36 RC 20211108.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 08 Nov '21

08 Nov '21

Announcing the creation of a new nightly release validation test event for Fedora-IoT 36 RC 20211108.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/36iot You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_36_RC_20211108.0_Sum… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_36_RC_20211108.0_Gen… Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

1 0

Proposal to CANCEL: 2021-11-08 Fedora QA Meeting
by Adam Williamson 05 Nov '21

05 Nov '21

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have anything urgent for this week, and it'd probably be more useful to have one next week after some of the things currently in discussion move forward a bit. If you're aware of anything it would be useful to discuss this week, please do reply to this mail and we can go ahead and run the meeting. Thanks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Fedora 35 QA Retrospective page is up
by Adam Williamson 05 Nov '21

05 Nov '21

So, the last of these emails I sent was eight years ago, time flies, huh? :) Sudhir suggested bringing these back, and it seemed like a fine idea, so I did! I've created a Fedora 35 Retrospective page: https://fedoraproject.org/wiki/Fedora_35_QA_Retrospective In the past we would've created this page *during* Fedora 35 validation, so we could note things as we went along. I'll try and remember to create one for Fedora 36 in a month or two. Just in case anyone wasn't around in 2013 :P, here's how it works! We use the retrospective page to track things that went well and things that didn't go so well during the Fedora 35 validation process, and for tracking ideas we have but don't have time to act on during the rush of doing validation (that's the wishlist). Please, add any feedback you have of this type to the retrospective page! There are instructions on the page for adding feedback. All feedback is useful, and after the page has been up for a while, we'll take a look at all the items on the page and come up with specific recommendations for addressing them which we'll file as issues and work on in the time before Fedora 36 validation starts up. You can look at the previous pages for inspiration: https://fedoraproject.org/wiki/Category:QA_Retrospective And once again I'll copy/paste James Laska's old list of leading questions to prompt feedback, because it's still pretty good: 1. Were you able to participate in any Fedora 35 Beta or Final test runs? 2. What worked well, what prevented you from participating, were instructions clear? 3. What worked (or didn't work) well about Fedora Test Days this release? 4. Are you a maintainer, why do you think your critpath updates haven't been tested? What could you do to encourage more testing of your proposed updates? 5. Did you escalate any bugs for consideration as {Beta,Final} release Blockers? Why not? Was the process well documented and did it make sense? 6. Did you attend or contribute to any Fedora blocker meetings? Why not? What did you like, dislike? What prevented you from participating? 7. Did you find any of the release criteria changes or validation test extensions particularly useful or problematic? 8. Can you think of any obviously important areas we are not currently covering in the validation tests and criteria? 9. How are you finding the tools that we use for the process, like the blocker bugs tool and the test day results tool? 10. Unlimited time and resource ... what do you think the the QA team should focus on for Fedora 36 and beyond </pony> -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Fedora 36 Rawhide 20211103.n.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 03 Nov '21

03 Nov '21

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce November 2021