/srv/irclogs.ubuntu.com/2024/04/30/#ubuntu-meeting.txt

=== dviererbe1 is now known as dviererbe
=== pushkarnk1 is now known as pushkarnk
sarnoldgood morning14:31
eslerm_good morning o/14:31
cpaelzeruuuh14:33
slyonhello! o/14:33
cpaelzerlate - sry14:33
cpaelzer#startmeeting Weekly Main Inclusion Requests status14:34
meetingologyMeeting started at 14:34:11 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology14:34
meetingologyAvailable commands: action, commands, idea, info, link, nick14:34
cpaelzerPing for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )14:34
jamespageo/14:34
cpaelzerso Oraculus Oraculous Ora... I still need to get this into my fingers14:34
cpaelzerit opened14:34
cpaelzerso we might see new things soon14:34
cpaelzer#topic current component mismatches14:34
cpaelzerMission: Identify required actions and spread the load among the teams14:34
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg14:34
cpaelzer#link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg14:34
cpaelzerit is https://launchpad.net/ubuntu/oracular14:35
cpaelzerok, no syncs or uploads yet14:35
cpaelzerand noble is stable in regard to uploads14:35
sarnoldis that large 'beta' banner new?14:35
cpaelzerok, next section14:35
cpaelzerI do not remember it from past releases14:35
cpaelzerbut could not guarantee that it is super new14:35
sarnoldah focal has one too :) https://launchpad.net/ubuntu/focal14:35
cpaelzer#topic New MIRs14:36
cpaelzerMission: ensure to assign all incoming reviews for fast processing14:36
cpaelzer#link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir14:36
sarnoldit must be the section, hehe14:36
cpaelzerI think that is for Buster not for Focal14:36
cpaelzeranyway not going into that, also suggesting trixie here14:36
cpaelzerno new open bugs14:36
cpaelzer#topic Incomplete bugs / questions14:36
cpaelzerMission: Identify required actions and spread the load among the teams14:37
cpaelzer#link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir14:37
cpaelzeronly recent update is14:37
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/nbd/+bug/205448014:37
-ubottu:#ubuntu-meeting- Launchpad bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, Incomplete]14:37
cpaelzerok, sarnold got to the shallow review we wanted14:37
cpaelzerthakns14:37
cpaelzerwe won't add it to Noble based on that14:38
cpaelzerbut that means it is unblocked for 24.10 right?14:38
sarnoldyes, or 24.04.1 ought to be fine, too14:39
cpaelzerthe required TODOs are still a few non-trivial tests14:39
cpaelzerand consider adding confinement as recommended todo14:39
cpaelzerIIRC there were answers to that14:39
cpaelzerchecking ...14:39
cpaelzerhttps://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054480/comments/414:40
-ubottu:#ubuntu-meeting- Launchpad bug 2054480 in nbd (Ubuntu) "[MIR] nbd-client" [Undecided, Incomplete]14:40
sarnoldconfining all the things would be nice, yeah, but the primary use of nbd-client is likely during early boot with 'fixed' values .. the remote peer will be serving a filesystem, so very very powerful14:40
cpaelzeryes, the isolation is a "try to" ask14:41
cpaelzerbut the testing that was mentioned has not landed yet14:41
cpaelzerI think the order from here is14:41
cpaelzer1. land the testing that they mentions14:41
cpaelzer2. continue trying to confine if possible14:41
cpaelzer3. SRU at least the testing14:41
cpaelzeractually 3. promoting in 24.1014:42
cpaelzerthen SRU14:42
cpaelzerand then consider promoting in 24.04.114:42
slyonwaveform: ^14:42
cpaelzerupdated the case14:44
cpaelzer#topic Process/Documentation improvements14:44
cpaelzerMission: Review pending process/documentation pull-requests or issues14:44
cpaelzer#link https://github.com/canonical/ubuntu-mir/pulls14:44
cpaelzer#link https://github.com/canonical/ubuntu-mir/issues14:44
cpaelzernothing new14:44
eslerm_I added to my end-of-cycle comment14:45
waveformslyon, thanks -- I'll stick those on my todo list14:45
cpaelzerI see14:45
eslerm_an issue from the late cycle request of qrtr/protection-domain-mapper is causing issues14:45
cpaelzerthe arm64 issues you mean?14:45
eslerm_yes14:45
cpaelzerI wasn't even aware of those late additions14:45
cpaelzeroh that is the x13s story14:46
eslerm_they were a late ask in mantic14:46
sarnoldI think xn_ox bought a new laptop :)14:46
cpaelzerok, it is a good "another example" to the problem overall14:46
cpaelzerthanks eslerm_14:46
cpaelzerThe action still didn't change14:46
eslerm_the packages looked dangerous, but were ack'd exculsively for x13s hardware enablement14:46
cpaelzerHmm14:47
cpaelzerthat adds the thought of "how to ensure limited acks stay limited"14:47
cpaelzerI have no great suggestion to make yet, need to ponder about that ...14:47
cpaelzerwe all might need to, let me go on with the agenda for now14:47
eslerm_+114:47
cpaelzer#topic Any other business?14:48
cpaelzeroh and more feedback on the topic above14:48
cpaelzeryou can be sure that I'll mention too huge too late changes in any 24.04 retrospective I'm in14:48
cpaelzernot sure it will change things, but it is the right thing to d14:48
cpaelzero14:48
cpaelzerother than that - nothing MIR'ish from me or server in general14:49
sarnoldare you thinking t64 or xz or boto?14:49
cpaelzer"or ..." and that is the problem14:49
cpaelzerbut more t64, crisis, ...14:49
cpaelzerhuge things we could have done otherwise14:49
cpaelzernot so much xz and boto which just fell onto us14:49
cpaelzerbut that is opinion14:49
sarnoldt64 really ought to have been done 22.10 or so14:50
cpaelzerif we could keep the things we control in -dev14:50
cpaelzerthat would help14:50
sarnoldmany things only happen when they become a crisis .. alas i'm guilty of this myself14:50
cpaelzeryeah sarnold, exactly what you say14:50
cpaelzeranything else else?14:51
sarnoldnone here14:51
slyonnothing from my side14:51
cpaelzerthis is the last agenda item, so next would otherwise be closing14:51
sarnoldexcept to idly wonder what the next t64 is :)14:51
eslerm_none for me14:51
cpaelzersarnold: that is for a talk at beer'o'clock - not for this meeting14:51
cpaelzerok, thank you all14:51
cpaelzerclosing14:51
cpaelzer#topic Any other business?14:51
sarnoldooo lucky you, already ti feierabend :)14:51
sarnoldbeer oclcock is a looong ways off..14:52
eslerm_o/14:52
sarnoldcpaelzer: btw that wasn't the usual #endmeeting :)14:52
cpaelzerhehe14:52
cpaelzerbad copy pasta14:52
sarnoldthanks cpaelzer, all :)14:52
cpaelzer#endmeeting14:53
meetingologyMeeting ended at 14:53:00 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2024/ubuntu-meeting.2024-04-30-14.34.moin.txt14:53

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!