/srv/irclogs.ubuntu.com/2023/11/29/#ubuntu-meeting.txt

=== ddstreet_away is now known as ddstreet
ddstreeto/16:02
ddstreetmapreri teward around?16:02
teward*flops in*16:03
ddstreetgood morning!16:03
tewardsend coffee16:03
tewardgenii: go fetch The Big Coffee Pot, the caffeine is required!16:03
teward:P16:03
ddstreetmust have caffeine!16:04
ddstreetnot sure if mapreri is able to make it today, i don't think he accepted the invite16:04
ddstreeti guess let's give him a few more minutes and then start16:05
tewardgood that lets me brew a coffee xD16:06
ddstreetok ready when you are teward16:08
tewardye gimme a minute16:09
tewardcoffee maker is slow to heat today16:09
ddstreeti'll go ahead and start just to get thru the administrative previous action item stuff16:10
ddstreet#startmeeting Ubuntu Backports Team16:10
meetingologyMeeting started at 16:10:26 UTC.  The chair is ddstreet.  Information about MeetBot at https://wiki.ubuntu.com/meetingology16:10
meetingologyAvailable commands: action, commands, idea, info, link, nick16:10
ddstreet#topic previous action items16:10
ddstreeti think almost all these are carry-overs so i'll run through them quick16:10
ddstreet#subtopic ddstreet get DEB_VENDOR=ubuntu dch --bpo to DTRT pls (carried over)16:11
ddstreet#action ddstreet get DEB_VENDOR=ubuntu dch --bpo to DTRT pls (carried over)16:11
meetingologyACTION: ddstreet get DEB_VENDOR=ubuntu dch --bpo to DTRT pls (carried over)16:11
ddstreet#subtopic ddstreet look at reviewer tooling such as 'queue' or other tools for reviewing/accepting/rejecting uploads, and closing the corresponding bugs (carried over)16:11
ddstreet#action ddstreet look at reviewer tooling such as 'queue' or other tools for reviewing/accepting/rejecting uploads, and closing the corresponding bugs (carried over)16:11
meetingologyACTION: ddstreet look at reviewer tooling such as 'queue' or other tools for reviewing/accepting/rejecting uploads, and closing the corresponding bugs (carried over)16:11
ddstreet#subtopic ddstreet send short policy wording proposal to ML regarding https://lists.ubuntu.com/archives/ubuntu-backports/2023-March/023030.html16:11
ddstreet#action ddstreet send short policy wording proposal to ML regarding https://lists.ubuntu.com/archives/ubuntu-backports/2023-March/023030.html16:11
meetingologyACTION: ddstreet send short policy wording proposal to ML regarding https://lists.ubuntu.com/archives/ubuntu-backports/2023-March/023030.html16:11
ddstreet#subtopic ddstreet review cockpit backport uploads16:11
ddstreeti did this one! :-)16:11
ddstreet#subtopic ddstreet ping email to keep thread alive: clarification on specific wording for no-bug-required backport exceptions16:11
ddstreet#action ddstreet ping email to keep thread alive: clarification on specific wording for no-bug-required backport exceptions16:12
meetingologyACTION: ddstreet ping email to keep thread alive: clarification on specific wording for no-bug-required backport exceptions16:12
ddstreet#subtopic ddstreet sched next mtg oct 2516:12
ddstreetdid that one too! :)16:12
ddstreeti'll run thru mapreri's as well since he's not here16:12
ddstreet#subtopic mapreri upload (more of) all the tools (carried over, in progress)16:12
ddstreet#action mapreri upload (more of) all the tools (carried over, in progress)16:12
meetingologyACTION: mapreri upload (more of) all the tools (carried over, in progress)16:12
ddstreet#subtopic mapreri fix lintian to not complain about ~bpo suffix (https://bugs.debian.org/1001399) (carried over)16:12
-ubottu:#ubuntu-meeting- Debian bug 1001399 in lintian "lintian: adjust backports-upload-has-incorrect-version-number for ubuntu" [Normal, Open]16:12
ddstreet#action mapreri fix lintian to not complain about ~bpo suffix (https://bugs.debian.org/1001399) (carried over)16:12
meetingologyACTION: mapreri fix lintian to not complain about ~bpo suffix (https://bugs.debian.org/1001399) (carried over)16:12
ddstreet#subtopic mapreri review wiki page to see how we can highlight that backport requestors need to do the backport work and find a sponsor (carried over)16:12
ddstreet#action mapreri review wiki page to see how we can highlight that backport requestors need to do the backport work and find a sponsor (carried over)16:12
meetingologyACTION: mapreri review wiki page to see how we can highlight that backport requestors need to do the backport work and find a sponsor (carried over)16:12
ddstreet#subtopic mapreri start thread on ML about how to use bug status to define meaing in process (carried over)16:12
ddstreet#action mapreri start thread on ML about how to use bug status to define meaing in process (carried over)16:13
meetingologyACTION: mapreri start thread on ML about how to use bug status to define meaing in process (carried over)16:13
ddstreet#subtopic teward make sure there are no bugs in requestbackport and backportpackage tools (in lunar) (carried over)16:13
ddstreetassume i should carry this over teward?16:13
tewardye16:13
ddstreet#action teward make sure there are no bugs in requestbackport and backportpackage tools (in lunar) (carried over)16:13
meetingologyACTION: teward make sure there are no bugs in requestbackport and backportpackage tools (in lunar) (carried over)16:13
teward #NeverEnoughCycles16:13
ddstreet#subtopic (unassigned) consider documenting an SLA for reviewing uploaded backport packages16:13
ddstreet#action (unassigned) consider documenting an SLA for reviewing uploaded backport packages16:13
meetingologyACTION: (unassigned) consider documenting an SLA for reviewing uploaded backport packages16:13
ddstreet#subtopic (unassigned) check if backports pocket uploads and/or approvals go to a ML (carried over)16:13
ddstreet#action (unassigned) check if backports pocket uploads and/or approvals go to a ML (carried over)16:13
meetingologyACTION: (unassigned) check if backports pocket uploads and/or approvals go to a ML (carried over)16:13
ddstreet#subtopic (unassigned) if no ML for backports uploads/approvals, check on how to create one (carried over)16:14
ddstreet#action (unassigned) if no ML for backports uploads/approvals, check on how to create one (carried over)16:14
meetingologyACTION: (unassigned) if no ML for backports uploads/approvals, check on how to create one (carried over)16:14
ddstreetindeed i always think i'll be able to find time but rarely do16:14
ddstreetok that's all previous items16:14
ddstreet#topic open ML threads16:14
ddstreet#subtopic clarification on specific wording for no-bug-required backport exceptions16:14
ddstreet#link https://lists.ubuntu.com/archives/ubuntu-backports/2022-February/022680.html16:15
ddstreeti think we need to carry this one16:15
tewardyup16:15
ddstreet#action clarification on specific wording for no-bug-required backport exceptions (carried over)16:15
meetingologyACTION: clarification on specific wording for no-bug-required backport exceptions (carried over)16:15
ddstreet#subtopic staging grub 2.12 backports in backports pocket during 24.04 developement cycle16:16
ddstreet#link https://lists.ubuntu.com/archives/ubuntu-backports/2023-October/023128.html16:16
ddstreet#link https://lists.ubuntu.com/archives/ubuntu-backports/2023-November/023150.html (my reply asking for clarification)16:17
ddstreetteward not sure if you read his email yet, but i'm not totally clear on what he's asking about?16:17
ddstreetjuliank in case you're around ^16:18
tewardi havent - i have a ton of higher priority CC-hat emails drifting around16:18
ddstreetok, let's just leave this one in the ML then, my reply was recent so let's give him some time to follow up16:19
ddstreeti'll keep it on the open threads16:19
ddstreet#action staging grub 2.12 backports in backports pocket during 24.04 developement cycle16:19
meetingologyACTION: staging grub 2.12 backports in backports pocket during 24.04 developement cycle16:19
tewardi mean I don't see a benefit of this being in backports if its quirky and not stable16:19
ddstreetright, me neither16:19
ddstreeti assumed i must have misunderstood what he was proposing16:20
tewardgrub* is one of those things I dont think can be safely backported either without extreme care, hence why SRU/security processes cover it16:20
teward(using backports as staging isnt what backports is for)16:20
ddstreetyeah total agreement on that16:21
ddstreet#subtopic https://lists.ubuntu.com/archives/ubuntu-backports/2023-October/023129.html16:21
teward(this is what Experimental is for Debian Unstable but I digress)16:21
ddstreet#undo16:21
meetingologyRemoving item from minutes: SUBTOPIC16:21
ddstreet#subtopic Backport uploads to non-LTS releases16:21
ddstreet#link https://lists.ubuntu.com/archives/ubuntu-backports/2023-October/023129.html16:21
ddstreetthis is for the cockpit uploads to the non-LTS releases16:21
ddstreetour current policy is to only allow specifically exempted packages to get backported to non-LTS16:22
ddstreetmy email was just to revisit that (in general, not specifically for cockpit pkgs)16:22
tewardi think cockpit is an exception not the rule.  the problem with interim releases is a lot of times backporting in interim can happen but then get lost in the chain16:23
tewardhistorically it overloaded backporters16:23
ddstreetso it's probably better to keep the restriction but allow an exception for cockpit you think?16:23
ddstreeti'm fine either way, and i can see how it would overload us if it becomes more common16:24
tewardimo there will always be exceptions16:24
tewardon an adhoc basis or as needed16:24
tewardbut yes cockpit is one i would give as an exception16:24
tewardand also add to our no-bug-needed backports list (its a special case)16:24
ddstreeti don't think we currently have any formal exception process for it currently, you think we need to define one, or just have informal exception agreements during our normal meetings?16:25
tewardif it becomes more common, we can create formal processes.  for now as long as we are quorate on exceptions we should be OK16:25
tewardi dont see us granting a lot of exceptions16:26
ddstreetagreed16:26
ddstreetok so we're quorate (since we have 2/3 today) and we both agree to keep the non-LTS restriction but also to give an exception to cockpit (and cockpit-podman, cockpit-machines) for non-LTS and no-bug-required16:26
ddstreetright?16:27
ddstreeti can update our wiki page to add its exception if so16:27
tewardif you are in agreement with me on all that then yes16:27
ddstreetyep i am16:27
ddstreetok i'll update the exception list16:27
tewardthen go right ahead and update the wiki16:27
tewardyep16:27
ddstreet#action ddstreet update exception list to add cockpit, cockpit-machines, cockpit-podman16:28
meetingologyACTION: ddstreet update exception list to add cockpit, cockpit-machines, cockpit-podman16:28
ddstreet#link https://wiki.ubuntu.com/UbuntuBackports#Allowed_in_non-LTS_releases16:28
ddstreetfor my reference16:28
ddstreetok i think that's all the ML threads unless i missed something16:28
ddstreet#topic open bugs needing discussion16:29
ddstreetI don't see any open bugs, and i went through the upload queues earlier today16:29
ddstreeti'll handle the cockpit uploads to non-LTS releases16:29
ddstreet#action ddstreet review cockpit uploads to non-LTS releases16:29
meetingologyACTION: ddstreet review cockpit uploads to non-LTS releases16:29
tewardperfect16:29
ddstreet#topic AOB16:30
ddstreeti think we've covered everything?16:30
ddstreetanything else?16:30
tewardddstreet: make a note that exceptions are evaluated on a case by case basis16:30
ddstreetyep16:30
ddstreet#action ddstreet note in wiki exceptions are evalated on a case by case basis16:30
meetingologyACTION: ddstreet note in wiki exceptions are evalated on a case by case basis16:30
ddstreetnext mtg date?16:31
ddstreet#subtopic next mtg date16:31
ddstreeti think 4 wks gets into the holidays16:31
tewardand are for exceptional cases NOT regular cases (so there has to be real strong support for an exception case for it to be approved)16:31
tewardye 4 weeks is right in holiday weeks16:31
tewardwe may be able to skip and just do an early january meeting in place of it16:31
tewardif theres no objections16:31
ddstreetyeah let's move it to jan16:31
ddstreetworks for me16:32
teward(email mapreri though to make sure they are OK with it)16:32
ddstreetyep16:32
ddstreet#action ddstreet email mapreri (and list) to pick next mtg date (probably in jan)16:32
meetingologyACTION: ddstreet email mapreri (and list) to pick next mtg date (probably in jan)16:32
ddstreeti think either jan 3 or jan 10 is most likely, probably jan 10 in case any of us is out right after the new year16:33
ddstreetbut i'll email16:33
tewardi'm always around by jan3 xD16:33
ddstreetlol i *probably* will be over my hangover by then ;-)16:33
tewardIT Security never sleeps though so.  :P16:33
ddstreetyeah you might be around jan 1 in that line of work :)16:34
tewardwell thats a day off but technically you're right16:34
tewardemergency or smth16:34
ddstreethope that pager doesn't go off at 12:01am jan 1 ;-P16:34
tewardlol16:34
tewardwell i am gonna go get food i'm hungry16:35
ddstreetsounds good and i think we're wrapped up!16:35
ddstreetthanks!16:35
tewardif theres no other business?16:35
tewardperfect thank you!  *disappears to lunch*16:35
ddstreet#endmeeting16:35
meetingologyMeeting ended at 16:35:23 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-11-29-16.10.moin.txt16:35
ddstreetthanks! o/16:35
juliankddstreet: I'll reply on the mailing list, I lost track of it, but suffice it to say: currently all releases are on 2.06; they'll all be on 2.12 in like May, but we want people to be able to try out 2.12 before that easily (and keep -proposed free for critical 2.06 updates)16:39
* genii slides the industrial sized vat of tepid coffee in teward's direction 17:22

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