2025-06-04 20:26:27 <@cmurf:fedora.im> !startmeeting Workstation WG - 2025-06-03 2025-06-04 20:26:28 <@meetbot:fedora.im> Meeting started at 2025-06-04 20:26:27 UTC 2025-06-04 20:26:28 <@meetbot:fedora.im> The Meeting name is 'Workstation WG - 2025-06-03' 2025-06-04 20:26:35 <@cmurf:fedora.im> 2025-06-04 20:26:35 <@cmurf:fedora.im> !info Present members: Michael, Matthias, Chris, Allan, Michel, Nieves 2025-06-04 20:26:35 <@cmurf:fedora.im> !info Regrets: 2025-06-04 20:26:35 <@cmurf:fedora.im> !info Missing: 2025-06-04 20:26:35 <@cmurf:fedora.im> !info Secretary: Allan 2025-06-04 20:26:35 <@cmurf:fedora.im> !info Guests: Barry, Bohdan, Lee 2025-06-04 20:26:35 <@cmurf:fedora.im> 2025-06-04 20:26:35 <@cmurf:fedora.im> !topic Update policy 2025-06-04 20:26:35 <@cmurf:fedora.im> We had some major breakage due to a Mutter update. A lot of users were affected. In this case the update went to stable very quickly. 2025-06-04 20:26:35 <@cmurf:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2369567 2025-06-04 20:26:35 <@cmurf:fedora.im> Could our update policy prevent this type of issue? For example, we could keep updates in testing for a longer period of time. 2025-06-04 20:26:35 <@cmurf:fedora.im> Counter argument - core/important packages could have a longer test period. 2025-06-04 20:26:35 <@cmurf:fedora.im> A longer test period would increase the time required to fix regressions. 2025-06-04 20:26:35 <@cmurf:fedora.im> !link https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#karma-requirements 2025-06-04 20:26:35 <@cmurf:fedora.im> We have the authority to set our own updates policy. 2025-06-04 20:26:35 <@cmurf:fedora.im> Currently policy is: 2025-06-04 20:26:35 <@cmurf:fedora.im> +3 karma or 7 days in testing with no negative karma. 2025-06-04 20:26:35 <@cmurf:fedora.im> For critical path updates, +3 karma or 14 days with no negative karma. Critical path is defined in comps. 2025-06-04 20:26:35 <@cmurf:fedora.im> We think that it's possible that negative karma disables automatic push, but it is possible to reenable it. 2025-06-04 20:26:35 <@cmurf:fedora.im> Allan: a minimum testing period would make sense, irrespective of the amount of positive karma an update receives. 2025-06-04 20:26:35 <@cmurf:fedora.im> We can override the policy for special cases, if necessary? 2025-06-04 20:26:35 <@cmurf:fedora.im> !agreed We would like to add a minimum test period to the policy. 2025-06-04 20:26:35 <@cmurf:fedora.im> 2025-06-04 20:26:35 <@cmurf:fedora.im> !action Nieves to talk to Adam about making the change 2025-06-04 20:26:35 <@cmurf:fedora.im> !topic Announcements, follow-ups, status reports 2025-06-04 20:26:35 <@cmurf:fedora.im> !meetingname workstation 2025-06-04 20:26:35 <@cmurf:fedora.im> !chair Matthias 2025-06-04 20:26:35 <@cmurf:fedora.im> !link https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org/message/THPOLJYF7XKAYXPRNJFV7AKWZMW3V4CF/ 2025-06-04 20:26:35 <@cmurf:fedora.im> 2025-06-04 20:26:35 <@cmurf:fedora.im> Matthias gave a workstation update at the Fedora release party last Thursday. I hope it went ok. 2025-06-04 20:26:35 <@cmurf:fedora.im> Potential future topic: invite Adrian Vovk to talk about his work on gdm and gnome-session. 2025-06-04 20:26:35 <@cmurf:fedora.im> Flock is happening this week 2025-06-04 20:26:35 <@cmurf:fedora.im> 2025-06-04 20:26:35 <@cmurf:fedora.im> !topic Open Floor 2025-06-04 20:26:35 <@cmurf:fedora.im> 2025-06-04 20:26:35 <@cmurf:fedora.im> !topic Gemini notes for this meeting 2025-06-04 20:26:35 <@meetbot:fedora.im> The Meeting Name is now workstation 2025-06-04 20:26:58 <@cmurf:fedora.im> !endmeeting