desktop April 2022

desktop@lists.stg.fedoraproject.org

12 participants
23 discussions

2022-04-04 @ 16:00 UTC - Fedora 36 Blocker Review Meeting
by Adam Williamson 01 Apr '22

01 Apr '22

# F36 Blocker Review meeting # Date: 2022-04-04 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 9 proposed Final blockers and 3 proposed Final freeze exception issues to review, so let's have a review meeting on Monday. Note, I won't be around to run this one - you'll be in the capable hands of Geoff (coremodule). 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 Geoff will 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

1 0

Fedora 36 validation testing event: let's do full testing of Fedora 36 Branched 20220401.n.0
by Adam Williamson 01 Apr '22

01 Apr '22

Hi folks! Trying something a bit new here. I've nominated today's Fedora 36 nightly compose for validation testing. We do this regularly in any case, but I'm sending this out to a wider group and asking folks to treat this nightly as it it were a release candidate, and try to complete the *full* set of Final validation tests on it. The idea is to try and make sure we get all the tests done well ahead of the Go/No-Go Meeting, so we can identify any remaining blocker bugs *now*, not have to try and deal with them in a hurry later. Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/36 . You can use this to prioritize tests that have not yet been run at all. 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_36_Branched_20220401.n.0… The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… https://fedoraproject.org/wiki/Test_Results:Fedora_36_Branched_20220401.n.0… The goal is to try and hit every test marked as Basic, Beta or Final (hitting the Optional ones too is great but not required). It'd be particularly good to cover things that often don't get done until late - aarch64 tests, Cloud tests in real clouds, and the full set of Server Active Directory tests, for instance. If you hit a significant failure in a test, please file a bug, and most likely propose it as a release blocker using https://qa.fedoraproject.org/blockerbugs/propose_bug . If you have any questions or need any help with testing or reporting results, please contact us on the test@ list or the QA IRC/Matrix channel (#fedora-qa on IRC, "Fedora QA (Quality Assurance)" on Matrix). Thanks a lot, folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Workstation WG meeting, 5 April (secretary: Matthias)
by Allan Day 01 Apr '22

01 Apr '22

Hi all, The next meeting of the Fedora Workstation Working Group is planned for Tuesday 5 April, at 9.30 EDT. Join links: https://bluejeans.com/395383051/ https://www.bluejeans.com/numbers See below for the agenda. Allan -- Agenda #topic Fedora 36: Workstation blockers and priorities #link https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.o… What happened with Michael's F36 printing issues? #topic Give ABRT some ❤ #link https://pagure.io/fedora-workstation/issue/130 #topic Red Hat Bugzilla: GNOME packages are in bad shape #lisk https://pagure.io/fedora-workstation/issue/131 #topic The Workstation Working Group is a bottleneck #link https://pagure.io/fedora-workstation/issue/218 #topic Workstation user and contributor community on discussion.fedoraproject.org #link https://pagure.io/fedora-workstation/issue/223 #topic Consolidate and advertise Workstation chat channels #link https://pagure.io/fedora-workstation/issue/224 #topic Parental Controls app getting poor reviews #link https://pagure.io/fedora-workstation/issue/263 #topic Announcements, Status Updates #info Meeting minutes from last week posted #link https://meetbot.fedoraproject.org/fedora-meeting-2/2022-03-29/workstation.2…

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop April 2022