October 2021 - test-announce - Fedora Mailing-Lists

Proposal to CANCEL: 2021-10-18 Fedora QA Meeting

by Adam Williamson

[re-send with correct date, sorry] Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have much for the agenda, and we're in F35 Final crunch mode ATM. There will be a blocker review meeting. 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

2 years, 6 months

1
0
0 / 0

Proposal to CANCEL: 2021-10-11 Fedora QA Meeting

by Adam Williamson

Hi folks! I'm proposing we cancel the QA meeting on Monday. I don't have much for the agenda, and we're in F35 Final crunch mode ATM. There will be a blocker review meeting. 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

2 years, 6 months

1
0
0 / 0

Fedora Linux 35 Final is NO-GO

by Ben Cotton

Due to outstanding blocker bugs[1], we do not have an F35 Final RC. As a result, F35 Final is NO-GO by default and tomorrow's Go/No-Go meeting is cancelled. The next Fedora Linux 35 Final Go/No-Go meeting[2] will be held at 1700 UTC on Thursday 21 October in #fedora-meeting. We will aim for the "target date #1" milestone of 26 October. The release schedule[3] has been updated accordingly. [1] https://qa.fedoraproject.org/blockerbugs/milestone/35/final/buglist [2] https://calendar.fedoraproject.org/meeting/10102/ [3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

2 years, 6 months

1
0
0 / 0

Fedora 35 Branched 20211013.n.0 nightly compose nominated for testing

by rawhide＠fedoraproject.org

Announcing the creation of a new nightly release validation test event for Fedora 35 Branched 20211013.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 - 20211010.n.0: anaconda-35.22.2-1.fc35.src, 20211013.n.0: anaconda-35.22.2-2.fc35.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/35 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_35_Branched_20211013.n... The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211013.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211013.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211013.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211013.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211013.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211013.n... Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

2 years, 6 months

1
0
0 / 0

Fedora 35 Branched 20211010.n.0 nightly compose nominated for testing

by rawhide＠fedoraproject.org

Announcing the creation of a new nightly release validation test event for Fedora 35 Branched 20211010.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: lorax - 20211004.n.0: lorax-35.7-1.fc35.src, 20211010.n.0: lorax-35.7-2.fc35.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/35 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_35_Branched_20211010.n... The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211010.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211010.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211010.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211010.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211010.n... https://fedoraproject.org/wiki/Test_Results:Fedora_35_Branched_20211010.n... Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

2 years, 6 months

1
0
0 / 0

2021-10-11 @ 16:00 UTC - Fedora 35 Blocker Review Meeting

by Adam Williamson

# F35 Blocker Review meeting # Date: 2021-10-11 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 6 proposed Final blockers and 1 proposed Final freeze exceptions to review, so let's have a review meeting on Monday. 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 F35 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 on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

2 years, 6 months

1
0
0 / 0

Fedora Linux 35 Final Go/No-Go meeting next week

by Ben Cotton

Hi everyone, It's that time already! The Fedora Linux 35 Fina Go/No-Go[1] meeting is scheduled for Thursday 14 October at 1700 UTC in #fedora-meeting. At this time, we will determine the status of the F35 Final for the 19 October early target date[2]. For more information about the Go/No-Go meeting, see the wiki[3]. [1] https://calendar.fedoraproject.org/meeting/10098/ [2] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [3] https://fedoraproject.org/wiki/Go_No_Go_Meeting -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

2 years, 6 months

1
0
0 / 0

Fedora-IoT 35 RC 20211007.0 nightly compose nominated for testing

by rawhide＠fedoraproject.org

Announcing the creation of a new nightly release validation test event for Fedora-IoT 35 RC 20211007.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/35iot 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_35_RC_20211007.0_S... The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_35_RC_20211007.0_G... Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

2 years, 6 months

1
0
0 / 0

Fedora 35 Final Freeze

by Mohan Boddu

Hi all, Today, Oct 5th 2021, is an important day on the Fedora 35 schedule [1], with significant cut-offs. Today we have the Final Freeze [2] which starts at 14:00 UTC. This means that only packages which fix accepted blocker or freeze exception bugs [3][4][5] will be marked as 'stable' and included in the Final composes. Other builds will remain in updates-testing until the Final release is approved, at which point the Final freeze is lifted and packages can move to the 'updates' repository, pending updates will be pushed before final release as zero day updates. [1] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html [2] https://fedoraproject.org/wiki/Milestone_freezes [3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [5] https://qa.fedoraproject.org/blockerbugs/milestone/34/final/buglist Regards, Mohan Boddu Release Engineering

2 years, 6 months

1
0
0 / 0

** UPDATE ** 2021-10-08 @ 16:00 UTC - Special Fedora QA Meeting: Wireplumber Decision

by Adam Williamson

UPDATE: first time in eleventy billion years, and I messed it up...this meeting will be in #fedora-meeting-1, not #fedora-meeting, because ELN is using #fedora-meeting at that time. Apologies. # Special Fedora Quality Assurance Meeting # Date: 2021-10-08 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: ** #fedora-meeting-1 ** on irc.libera.chat Greetings testers! Well, this is exciting. I've been doing this job for approximately eleventy billion years, but I think this is the first time I'm going to run a special meeting! Today FESCo considered[0] a proposal[1] to trigger the contingency plan on the Fedora 35 Wireplumber change[2], which would mean going back to pipewire's own simple session manager. The decision they reached was that they'd give the maintainers until Friday to make improvements to Wireplumber, and on Friday, we (QA) get to decide if we think it's good enough to be shipped for Final. If by Friday we think it's not going to be in good enough shape for release, we'll immediately revert to the simple session manager - the changes to do so will be prepared and ready to go if necessary. This meeting will be at 16:00 UTC, which is 9am timezone, to give me enough time to check in on the status of all the bugs before we get started. Anyone interested is welcome to attend, and I expect we'll make the decision by rough consensus without worrying too hard about bureaucracy or who's allowed to have an opinion. If it somehow turns out to be especially controversial I'll try and come up with a voting system on the fly, if it gets really bad we can bounce it back to FESCo. == Proposed Agenda Topics == 1. Should we revert to the simple session manager, or stick with Wireplumber? [0] https://meetbot-raw.fedoraproject.org/teams/fesco/fesco.2021-10-04-19.03.... [1] https://pagure.io/fesco/issue/2670 [2] https://fedoraproject.org/wiki/Changes/WirePlumber -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

2 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce October 2021