==============================================
#fedora-meeting-2: Workstation WG (2022-08-30)
==============================================
Meeting started by brainycmurf at 16:23:31 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-08-30/workstation.2…
.
Meeting summary
---------------
* Present members: Allan, Jens, Kalev, Chris, Michael, Matthias, Neal
(brainycmurf, 16:23:47)
* Guests: Luna Jernberg(bittin), Zac (brainycmurf, 16:23:47)
* Regrets: Owen (brainycmurf, 16:23:47)
* Missing: (brainycmurf, 16:23:47)
* Secretary: Jens (brainycmurf, 16:23:47)
* F37 release status (brainycmurf, 16:23:48)
* Currently things are looking quite good - probably cannot get 43.rc
into Beta. (brainycmurf, 16:23:50)
* LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/37/beta/buglist
(brainycmurf, 16:23:52)
* LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist
(brainycmurf, 16:23:54)
* Workstation issues here: (brainycmurf, 16:23:58)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2111025
(gnome-shell) (brainycmurf, 16:24:00)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2121110
(gnome-initial-setup) (brainycmurf, 16:24:02)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2111003
(gnome-contacts) (brainycmurf, 16:24:04)
* ACTION: Matthias to check with Florian about the shell screen
recording issue (brainycmurf, 16:24:06)
* ACTION: Kalev to investigate the gnome-initial-setup issue
(brainycmurf, 16:24:08)
* ACTION: Allan to comment on the contacts issue (brainycmurf,
16:24:10)
* openh264 isn't getting pulled into new installs like we thought it
should be, due to a DNF change. (brainycmurf, 16:24:12)
* ACTION: Tomas to get the package list and add them to gnome-sig
(brainycmurf, 16:24:21)
* LINK: https://pagure.io/fesco/issue/2858 (brainycmurf, 16:24:23)
* AGREED: We'll target 7 September. If we slip by a day, we slip by a
day. (brainycmurf, 16:24:38)
* Reduce default service timeout to 15s (brainycmurf, 16:24:43)
* LINK: https://pagure.io/fedora-workstation/issue/163 (brainycmurf,
16:24:45)
* Issues with device security panel in F37 (brainycmurf, 16:24:53)
* LINK: https://pagure.io/fedora-workstation/issue/331 -- (Ubuntu is
also discussing this heavily) (brainycmurf, 16:24:55)
* AGREED: Keep the panel for F37 (brainycmurf, 16:25:07)
* Make more GNOME Circle apps available out of the box (brainycmurf,
16:25:09)
* LINK: https://pagure.io/fedora-workstation/issue/330 (brainycmurf,
16:25:11)
* Release blocking criteria for preinstalled apps (brainycmurf,
16:25:19)
* LINK: https://pagure.io/fedora-workstation/issue/304 (brainycmurf,
16:25:21)
* Announcements, Status Updates (brainycmurf, 16:25:25)
* The minutes from last week have been posted. (brainycmurf,
16:25:29)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-08-24/workstation.2…
(brainycmurf, 16:25:31)
* gnome-info-collect was released last week to help gnome to collect
telemetry:
https://blogs.gnome.org/aday/2022/08/25/help-improve-gnome/
(brainycmurf, 16:25:34)
* LINK:
https://fedoraproject.org/wiki/Test_Day:2022-09-06_I18N_Test_Day
(brainycmurf, 16:25:37)
Meeting ended at 16:46:35 UTC.
Action Items
------------
* Matthias to check with Florian about the shell screen recording issue
* Kalev to investigate the gnome-initial-setup issue
* Allan to comment on the contacts issue
* Tomas to get the package list and add them to gnome-sig
Action Items, by person
-----------------------
* Allan
* Allan to comment on the contacts issue
* **UNASSIGNED**
* Matthias to check with Florian about the shell screen recording
issue
* Kalev to investigate the gnome-initial-setup issue
* Tomas to get the package list and add them to gnome-sig
People Present (lines said)
---------------------------
* brainycmurf (56)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
Hey folks! I apologize for the wide distribution, but this seemed like
a bug it'd be appropriate to get a wide range of input on.
There's a bug that was proposed as an F37 Beta blocker:
https://bugzilla.redhat.com/show_bug.cgi?id=1907030
it's quite an old bug, but up until recently, the summary was
apparently accurate - dnf would run out of memory with 512M of RAM, but
was OK with 1G. However, as of quite recently, on F36 at least (not
sure if anyone's explicitly tested F37), dnf operations are commonly
failing on VMs/containers with 1G of RAM due to running out of RAM and
getting OOM-killed.
There's some discussion in the bug about what might be causing this and
potential ways to resolve it, and please do dig into/contribute to that
if you can, but the other question here I guess is: how much do we care
about this? How bad is it that you can't reliably run dnf operations on
top of a minimal Fedora environment with 1G of RAM?
This obviously has some overlap with our stated hardware requirements,
so here they are for the record:
https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/welcome/Ha…
that specifies 2GB as the minimum memory for "the default
installation", by which I think it's referring to a default Workstation
install, though this should be clarified. But then there's a "Low
memory installations" boxout, which suggests that "users with less than
768MB of system memory may have better results performing a minimal
install and adding to it afterward", which kinda is recommending that
people do exactly the thing that doesn't work (do a minimal install
then use dnf on it), and implying it'll work.
After some consideration I don't think it makes sense to take this bug
as an F37 blocker, since it already affects F36, and that's what I'll
be suggesting at the next blocker review meeting. However, it does seem
a perfect candidate for prioritized bug status, and I've nominated it
for that.
I guess if folks can chime in with thoughts here and/or in the bug
report, maybe a consensus will emerge on just how big of an issue this
is (and how likely it is to get fixed). There will presumably be a
FESCo ticket related to prioritized bug status too.
Thanks folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
Hey folks!
So we're in freeze for Fedora 37 Beta now, and the first go/no-go
meeting should be on September 8.
It would be really great if we can get the validation tests run now so
we can find any remaining blocker bugs in good time to get them fixed.
Right now the blocker list looks short, but there are definitely some
tests that have not been run.
You can use the testcase_stats view to find tests that need running:
https://openqa.fedoraproject.org/testcase_stats/37/
For each validation test set (Base, Desktop etc.) it shows when each
test was last performed. So you can easily look for Basic and Beta
tests that have not yet been run. We need to run all of these.
You can enter results using `relval report-results`, or edit the
summary results page at
https://fedoraproject.org/wiki/Test_Results:Current_Summary . That's a
redirect link which will always point to the validation results page
for the currently-nominated compose, which right now is 20220826.n.0.
Sumantro will be running a validation 'test week' starting on
Wednesday, so you can drop by the Fedora Test Day room on
chat.fedoraproject.org to hang out with other testers and get any help
you need in testing. See
https://lists.fedoraproject.org/archives/list/test-announce@lists.fedorapro…
for that announcement.
Thanks folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
# 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
==============================================
#fedora-meeting-2: Workstation WG (2022-08-23)
==============================================
Meeting started by brainycmurf at 15:08:10 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-08-24/workstation.2…
.
Meeting summary
---------------
* Present members: Allan, Michael, Kalev, Matthias, Chris, Tomas, Jens,
Neal, Owen (brainycmurf, 15:08:26)
* Guests: Luna Jernberg (bittin), Sumantro, Jimmac (brainycmurf,
15:08:26)
* Regrets: (brainycmurf, 15:08:26)
* Missing: (brainycmurf, 15:08:26)
* Secretary: Michael (brainycmurf, 15:08:26)
* F37 release status (brainycmurf, 15:08:27)
* F37 beta freeze has just begun (brainycmurf, 15:08:29)
* Next GNOME development release is the RC on 2022-09-03
(brainycmurf, 15:08:31)
* Early target date for F37 beta is 2022-09-13 (brainycmurf,
15:08:33)
* Beta go/no-go meeting is 2022-09-08 (brainycmurf, 15:08:35)
* F37 beta blockers (brainycmurf, 15:08:37)
* LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/37/beta/buglist
(brainycmurf, 15:08:39)
* GNOME 43 test day results (brainycmurf, 15:08:45)
* LINK: https://testdays.fedoraproject.org/events/138 (brainycmurf,
15:08:47)
* Reduce default service timeout to 15s (brainycmurf, 15:09:26)
* LINK: https://pagure.io/fesco/issue/2853 (brainycmurf, 15:09:28)
* LINK: https://github.com/systemd/systemd/pull/18386 (brainycmurf,
15:09:30)
* ACTION: Chris to ask Anita if this can be changed upstream
(brainycmurf, 15:09:48)
* Evaluate the state of gnome-calendar (brainycmurf, 15:09:54)
* LINK: https://pagure.io/fedora-workstation/issue/306 (brainycmurf,
15:09:56)
* Release blocking criteria for preinstalled apps (brainycmurf,
15:10:32)
* LINK: https://pagure.io/fedora-workstation/issue/304 (brainycmurf,
15:10:34)
* Announcements, Status Updates (brainycmurf, 15:10:38)
* The minutes from last week have been posted. (brainycmurf,
15:10:40)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-08-17/workstation.2…
(brainycmurf, 15:10:42)
* KDE aKademy first week of October in Barcelona (brainycmurf,
15:10:45)
* LINK: http://akademy.kde.org/2022 (brainycmurf, 15:10:47)
* LINK:
https://docs.fedoraproject.org/en-US/workstation-working-group/prd/
(brainycmurf, 15:10:56)
* LINK:
https://docs.fedoraproject.org/en-US/workstation-working-group/schedule/
(brainycmurf, 15:11:00)
Meeting ended at 15:11:02 UTC.
Action Items
------------
* Chris to ask Anita if this can be changed upstream
Action Items, by person
-----------------------
* **UNASSIGNED**
* Chris to ask Anita if this can be changed upstream
People Present (lines said)
---------------------------
* brainycmurf (73)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
# 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