test-announce August 2022

test-announce@lists.fedoraproject.org

4 participants
16 discussions

Fedora-IoT 37 RC 20220831.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 31 Aug '22

31 Aug '22

Announcing the creation of a new nightly release validation test event for Fedora-IoT 37 RC 20220831.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/37iot 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_37_RC_20220831.0_Sum… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_37_RC_20220831.0_Gen… Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

1 0

[Call for Action] Fedora 37 Pre-Beta Validation Event kicks off 2022-08-31 through 2022-08-07
by Sumantro Mukherjee 29 Aug '22

29 Aug '22

Hey All, Some of you may know from my presentation at Nest '22 about the Validation events that are getting added! Historically, Fedora QA has relied on a lot of contributor feedback. Mostly, we have set up multiple ways how to capture the results and there has been no better time than to start capturing feedback about the composes as a part of the Release Validation Event! As the name suggests, we will be validating composes throughout a week and we will do it twice per cycle, once for pre-beta and other for pre-final. Validation Events such as this are done to invite more community folks to test the latest compose(s) for each day and help fill the Release Validation Matrix leading up to the Final Go/No-Go meeting. We will start this Validation Event with the compose for 2022-08-31[0] and the respective "current" validation page can be found [1]. As the days change, so will the latest composes and thus will be the current validation pages. Feel free to jump in anytime, and submit validation results on the "current" validation page. You can use "relval" [2] to submit reports for composes as well apart from the regular editing wiki pages. I will be posting about the new images and the QA candidates on this list every day and will be up for taking any question there is! [0] https://kojipkgs.fedoraproject.org/compose/branched/ [1] https://fedoraproject.org/wiki/Test_Results:Current_Summary [2] https://pagure.io/fedora-qa/relval -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

2022-08-29 @ 16:00 UTC - Fedora 37 Blocker Review Meeting
by Adam Williamson 27 Aug '22

27 Aug '22

# F36 Blocker Review meeting # Date: 2022-08-29 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 4 proposed Beta blockers and13 proposed Final blockers to review, so let's have a review meeting. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F36 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

2022-08-29 @ 15:00 UTC - Fedora QA Meeting
by Adam Williamson 27 Aug '22

27 Aug '22

# Fedora Quality Assurance Meeting # Date: 2022-08-29 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.libera.chat Greetings testers! We didn't meet for a couple of weeks, so let's get together and check in. 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. Kiwi TCMS evaluation results 3. Fedora 37 check-in 4. Test Day / community event status 5. Open floor -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Fedora 37 Branched 20220826.n.0 nightly compose nominated for testing
by Adam Williamson 26 Aug '22

26 Aug '22

Announcing the creation of a new nightly release validation test event for Fedora 37 Branched 20220826.n.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 Notable package version changes: None. Drunk with power, I did this all on my own. Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/37 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_37_Branched_20220826.n.0… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220826.n.0… Thank you for testing! -- Mail generated by adamwill and a text editor

1 0

Fedora 37 Bodhi updates-testing activation and Beta Freeze
by Tomas Hrcka 23 Aug '22

23 Aug '22

Hi all, Today's an important day on the Fedora 37 schedule[1], with several significant cut-offs. First of all, today is the Bodhi updates-testing activation point [2]. That means that from now all Fedora 37 packages must be submitted to updates-testing and pass the relevant requirements[3] before they will be marked as 'stable' and moved to the fedora repository. Today is also the Beta freeze[4]. This means that only packages which fix accepted blocker or freeze exception bugs[5][6] will be marked as 'stable' and included in the Beta composes. Other builds will remain in updates-testing until the Beta release is approved, at which point the Beta freeze is lifted and packages can move to 'stable' as usual until the Final freeze. Today is also the Software String freeze[7], which means that strings marked for translation in Fedora-translated projects should not now be changed for Fedora 37. Finally, today is the 'completion deadline' Change Checkpoint[8], meaning that Fedora 37 Changes must now be 'feature complete or close enough to completion that a majority of its functionality can be tested'. All tracking bugs should be on ON_QA state or later to reflect this. Regards Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release [4] https://fedoraproject.org/wiki/Milestone_freezes [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy [8] https://fedoraproject.org/wiki/Changes/Policy -- Tomas Hrcka fas: humaton Libera.chat: jednorozec

1 0

2022-08-22 @ 16:00 UTC - Fedora 37 Blocker Review Meeting
by Adam Williamson 22 Aug '22

22 Aug '22

# F36 Blocker Review meeting # Date: 2022-08-22 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 3 proposed Beta blockers, 1 proposed Beta freeze exception issue, and 13 proposed Final blockers to review, so let's have a review meeting. Note, I'll try and cut that number of Final blockers down before the meeting - it'll help if folks can vote ahead. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F36 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good night/day and see you tomorrow/later today! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Proposal to CANCEL: 2022-08-22 Fedora QA Meeting
by Adam Williamson 22 Aug '22

22 Aug '22

Hi folks! I'm proposing we cancel the QA meeting today/tomrrow. I don't have anything much for the agenda again. There will be a blocker review meeting, though. If you're aware of anything it would be useful to discuss this week, please do reply to this mail and we can run the meeting. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Fedora-IoT 37 RC 20220816.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 16 Aug '22

16 Aug '22

Announcing the creation of a new nightly release validation test event for Fedora-IoT 37 RC 20220816.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/37iot 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_37_RC_20220816.0_Sum… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_37_RC_20220816.0_Gen… Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

1 0

Fedora 37 Branched 20220816.n.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 16 Aug '22

16 Aug '22

Announcing the creation of a new nightly release validation test event for Fedora 37 Branched 20220816.n.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 Notable package version changes: anaconda - 20220813.n.0: anaconda-37.12-1.fc37.src, 20220816.n.0: anaconda-37.12.1-1.fc37.src parted - 20220813.n.0: parted-3.5-5.fc37.src, 20220816.n.0: parted-3.5-6.fc37.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/37 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_37_Branched_20220816.n.0… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220816.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220816.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220816.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220816.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220816.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_37_Branched_20220816.n.0… Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce August 2022