== Meeting information == * #ubuntu-meeting: Weekly Ubuntu Foundations team meeting, started by juliank, 30 Nov at 16:01 — 16:37 UTC. * Full logs at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-11-30-16.01.log.html == Meeting summary == === Lightning rounds === Discussion started by juliank at 16:01. * ''LINK:'' https://discourse.ubuntu.com/t/foundations-team-updates-thursday-30-november-2023/ (juliank, 16:01) === Release incoming bugs === Discussion started by juliank at 16:10. * ''LINK:'' http://reports.qa.ubuntu.com/reports/rls-mgr/rls-nn-incoming-bug-tasks.html#foundations-bugs (juliank, 16:11) * ''LINK:'' (ish) rls-mm-incoming-bug-tasks.html (juliank, 16:28) === Team proposed-migration report === Discussion started by juliank at 16:34. === AOB === Discussion started by juliank at 16:36. == People present (lines said) == * juliank (42) * schopin (8) * bdmurray (6) * enr0n (4) * bdrung (3) * meetingology (2) * adrien (2) * ravikant_ (1) * zhsj (1) * dviererbe (1) * ginggs (1) == Full log == 16:01 #startmeeting Weekly Ubuntu Foundations team 16:01 Meeting started at 16:01:32 UTC. The chair is juliank. Information about MeetBot at https://wiki.ubuntu.com/meetingology 16:01 \o 16:01 #topic Lightning rounds 16:01 Available commands: action, commands, idea, info, link, nick 16:01 o/ 16:01 o/ 16:01 #link https://discourse.ubuntu.com/t/foundations-team-updates-thursday-30-november-2023/ 16:05 o/ 16:06 I have no questions 16:07 People are still writing :) 16:08 Then my question is why? 16:08 Because we always think we have enough time, even though we clearly don't. 16:10 o/ 16:10 dviererbe: what is a "release timeline tool"? 16:10 #topic Release incoming bugs 16:11 #link http://reports.qa.ubuntu.com/reports/rls-mgr/rls-nn-incoming-bug-tasks.html#foundations-bugs 16:11 (sorry real links are internal right now) 16:11 I'll sort it today. 16:11 bug 2044623 we are basically done already 16:11 This will get fixed with 2.12 final shortly 16:12 bug 1969394 I think is desktop 16:12 bug 2042790 - schopin 16:13 Oh right, that. Yes, we should do that. 16:13 (it's already somewhere in my todolist) 16:14 schopin: I'll go tag and target it anyhow 16:14 thanks :) 16:14 bug 2043713 I suppose is more armhf security gcc flag fallout? 16:15 ah yes I remember 16:16 So the issue is that valgrind doesn't support the right stack layout or something I read earlier today 16:16 "maybe"? tbh I didn't try to fully understand the root cause 16:17 this should be the -fstack-clash-protection issue 16:23 bug 2045250 16:24 fheimes was notified about that bug off-band, and figured we'd want to fix this *before* we get customer complaints :) 16:24 sounds gtm 16:24 (for fstack-clash-protection: asked the security team again over mattermost, and will maybe switch to another communication channel if I don't get an answer) 16:25 tagging todo 16:25 bug 2015538 16:25 seems SEG is interested now 16:26 Let's skip that 16:26 Why is this on Foundations' radar? The MIR has been filed by Desktop. 16:26 dbus is foundations 16:26 like dbus-daemon is right now, so dbus-broker should be when it replaces it 16:27 Oh and there's an issue of reimplementing a missing feature, which would be for us to do according to slyon. 16:27 bug 2017401 I do not know what to do right now and I'm supposed to write a spec on this I think but need to find notes from Riga 16:28 Need to get to January to reconnect with vor_lon 16:28 #link (ish) rls-mm-incoming-bug-tasks.html 16:28 bug 2041518 16:28 this is for desktop 16:29 bug 2041831 16:31 I believe this seems like a pygobject issue for desktop to investigate, probably a type declared wrong somewhere? 16:31 I left comment to that effect on the bug 16:31 That's all for mm, ff is empty too, we only have one bug left for jj 16:31 bug 2039083 16:32 enr0n: systemd-networkd blocks on empty list when waiting for online ifaces in jammy it says 16:33 juliank: this is a can of worms. We need to implement our network-online spec basically. 16:33 systemd-networkd-wait-online is behaving correctly in that case, but people have been used to it being a no-op basically for a while 16:33 but I should comment on that so I will do so 16:34 OK I'll leave that with you 16:34 so, basically, they're holding it wrong? 16:34 #topic Team proposed-migration report 16:34 Unfortunately we don't have good data from last week and it's going to take forever to get through the list so... 16:34 I propose we skip this in the meeting and create an epic tomorrow with tasks in it 16:34 Then everyone can just pick one 16:35 sounds like a good plan. 16:36 #topic AOB 16:36 I will be out tomorrow 16:36 As will I 16:36 me too 16:37 Alright, that wraps this up I suppose 16:37 #endmeeting Generated by MeetBot 0.4.0 (https://wiki.ubuntu.com/meetingology)