test-announce September 2020

test-announce@lists.fedoraproject.org

6 participants
24 discussions

Fedora 33 Beta is NO-GO
by Ben Cotton 16 Sep '20

16 Sep '20

Due to outstanding unresolved blockers, there is no release candidate for Fedora 33 Beta yet. I am cancelling tomorrow's Go/No-Go meeting. Please update the Release Readiness wiki page[1] with your team's readiness if appropriate. The Fedora 33 Beta Go/No-Go meeting[3] will be held at 1700 UTC on Thursday 24 September in #fedora-meeting-1. We will target a 29 September release. The release schedule[4] has been updated accordingly. This change does not impact the final release date. Help is wanted with any of the outstanding blockers. [1] https://fedoraproject.org/wiki/Release_Readiness [2] https://apps.fedoraproject.org/calendar/meeting/9810/ [3] https://qa.fedoraproject.org/blockerbugs/milestone/33/beta/buglist [4] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 0

Fedora 33 Branched 20200916.n.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 16 Sep '20

16 Sep '20

Announcing the creation of a new nightly release validation test event for Fedora 33 Branched 20200916.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 - 20200912.n.0: lorax-33.8-2.fc33.src, 20200916.n.0: lorax-33.10-1.fc33.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/33 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_33_Branched_20200916.n.0… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200916.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200916.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200916.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200916.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200916.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200916.n.0… Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

1 0

Fedora-IoT 33 RC 20200916.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 16 Sep '20

16 Sep '20

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

1 0

[Test Day] Fedora Media Writer 2020-09-18
by Sumantro Mukherjee 14 Sep '20

14 Sep '20

Hey Testers, Friday, 2020-09-18 will be Fedora Media Writer Test Day[0]! This Test Day will focus on Fedora Media Writer. Fedora Media Writer is used for creating bootable flash drives on different operating systems and architectures. The tool is intended to be provided as the primary download option since Fedora 25, with the aim of lowering the barrier for potential users to try and install Fedora. In this test day, we aim to test Fedora 33 pre-release boot-media creation on Windows, OS X, and Fedora 31,32 and 33 specifically targeting the creation of ARM-bootable media to see whether it's working well enough and catch any remaining issues. It's also pretty easy to join in: all you'll need is 4GB flash drive/SD card (With all it's *data backed up*). As always, the event will be in #fedora-test-day on Freenode IRC. [0]: http://fedoraproject.org/wiki/Test_Day:2020-09-18_Fedora_Media_Writer -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

Fedora 33 Branched 20200912.n.0 nightly compose nominated for testing
by rawhide＠fedoraproject.org 12 Sep '20

12 Sep '20

Announcing the creation of a new nightly release validation test event for Fedora 33 Branched 20200912.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 - 20200906.n.0: anaconda-33.25.2-1.fc33.src, 20200912.n.0: anaconda-33.25.2-3.fc33.src Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/33 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_33_Branched_20200912.n.0… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_33_Branched_20200912.n.0… Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer

1 0

2020-09-14 @ 16:00 UTC - Fedora 33 Blocker Review Meeting
by Adam Williamson 11 Sep '20

11 Sep '20

# F33 Blocker Review meeting # Date: 2020-09-14 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 11 proposed Beta freeze exceptions and 3 proposed Final blockers to review, so let's have a Fedora 33 blocker review meeting on Monday! Above numbers are subject to change... 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/ . 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 F33 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 Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

2020-09-14 @ 15:00 UTC - Fedora QA Meeting
by Adam Williamson 11 Sep '20

11 Sep '20

# Fedora Quality Assurance Meeting # Date: 2020-09-14 # Time: 15:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: #fedora-meeting on irc.freenode.net Greetings testers! We didn't meet for a few 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. Fedora 33 status 3. Outstanding criteria proposals 4. Test Day / community event status 5. Open floor -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Fedora 33 Beta Go/No-Go and Release Readiness meetings
by Ben Cotton 09 Sep '20

09 Sep '20

Hi everyone, It's that time already! The Fedora 33 Beta Go/No-Go[1] and Release Readiness[2] meetings are scheduled for Thursday 10 September. As a reminder, please update the Release Readiness page[3] with your team's readiness if appropriate. We will use that to keep the Release Readiness meeting short and focused. [1] https://apps.fedoraproject.org/calendar/meeting/9804/?from_date=2020-09-07 [2] https://apps.fedoraproject.org/calendar/meeting/9805/ [3] https://fedoraproject.org/wiki/Release_Readiness -- Ben Cotton He / Him / His Senior Program Manager, Fedora & CentOS Stream Red Hat TZ=America/Indiana/Indianapolis

1 1

Blocker Review discussion tickets -- now available
by Kamil Paral 07 Sep '20

07 Sep '20

Hello everyone, I'd like to announce a new project of the QA team and an extension of the BlockerBugs App [1]. The blocker and freeze exception proposals can now not only be discussed during regular blocker review meetings [2], but also at any time through discussion tickets hosted on Pagure [3]. So even if you don't have time to participate in the meeting, you can still participate and vote in those discussion tickets. This will be mostly interesting to people who participated in blocker review meetings in the past, but we hope we can attract new participants this way. It is also very useful for package maintainers and developers, because they can now easily provide feedback regarding a proposed blocker or a freeze exception without attending a meeting at a particular time or diluting a technical discussion in Bugzilla. To participate, open the BlockerBugs App for a particular milestone (e.g. F33 Beta [4]) and you'll see "Vote!" and "Discuss" links for proposed/accepted blockers and freeze exceptions. Follow the links to see tickets where you can express your opinion (which should ideally reflect our release criteria [5]). You can vote according to the guide present at [3], please read it carefully. A bot is following each ticket, updating the voting summary, and accepting certain commands. Watching the Pagure repo [3] also gives you the option to get notified about every new proposed blocker/freeze exception. We've been using these discussions for a week or two now (I apologize for a late announcement) and so far our existing practice seems to be to vote for proposals throughout the week using these discussion tickets, close those which we can easily get enough votes and agree on, and discuss the remainder during the next blocker review meeting. So the regular blocker review meeting hasn't been replaced, but we use the discussion tickets to cut down on the meeting length. We're still trying to figure out the best approach to take here, so nothing is set in stone. The voting functionality itself is also still in development, we'll try to provide new features and improve the experience based on your feedback. I'll be happy to answer questions, if there are any. Thanks, Kamil Fedora QA PS: Development credits go to Lukas Brabec, Frantisek Zatloukal, Tim Flink, Josef Skladanka and Adam Williamson. [1] https://qa.fedoraproject.org/blockerbugs/ [2] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process [3] https://pagure.io/fedora-qa/blocker-review [4] https://qa.fedoraproject.org/blockerbugs/milestone/33/beta/buglist [5] https://fedoraproject.org/wiki/Fedora_Release_Criteria

1 0

[F33] i18n Test Day 2020-09-08
by Sumantro Mukherjee 07 Sep '20

07 Sep '20

Hey All, Fedora is a community-driven project which means a lot of our users use Fedora in multiple languages. The i18n Test day[0] is scheduled to test changes that are coming in F33 along with testing the regular GNOME apps in a multi-lingual environment. This test day will also benefit from testers, testing the same in Silverblue as well! [0] http://fedoraproject.org/wiki/Test_Day:2020-09-08_I18N_Test_Day -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

test-announce September 2020