12:02:57 #startmeeting CIP IRC weekly meeting 12:02:57 Meeting started Thu Apr 6 12:02:57 2023 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:02:57 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:02:57 The meeting name has been set to 'cip_irc_weekly_meeting' 12:03:03 #topic AI review 12:03:10 1. reach out to Greg regarding LTS (jan) 12:03:25 yeah, I still need to do that 12:04:05 any other AIs? from last week? 12:04:41 "Investigate ALSA bug report on v4.4-st38" 12:04:51 But I think that's already handled 12:04:55 it is 12:05:06 perfect 12:05:14 then let's move on 12:05:17 #topic Kernel maintenance updates 12:05:40 i finished and released 4.4-st and 4.4-cip 12:05:40 This week reported 4 new CVEs and 9 updated CVEs. 12:05:46 I am reviewing 5.10.177. 12:07:07 I am reviewing 5.10.177. 12:08:10 anything else? 12:08:47 3 12:08:48 2 12:08:50 1 12:08:52 #topic Kernel release status 12:09:01 4.4 12:09:04 4.4-st39 and 4.4-cip74 are out 12:09:17 4.4.302-cip74-rt43 is out. 12:09:22 perfect 12:09:27 4.19 12:09:30 one sec 12:09:36 uh, sorry 12:09:46 i was under the impression that i was supposed to release rt. did i get that wrong? 12:10:36 at least the least should have happened in a way that you, uli, can do it as well - that was my understanding 12:11:14 seems it didn't, did it? 12:11:49 4.4-rt is currently not up to date with 4.9/4.14-rt, and have partly backported series. 12:12:14 so you are still working on the backport? 12:12:20 I'd like to finish the backporting. 12:12:23 Yes. 12:12:33 that's ok with me. just needed clarification. 12:14:09 ok, then now: 12:14:11 4.19 12:14:23 I guess the next 4.4-rt one will be sooner than scheduled (it will be first one with specific -rt backports0. 12:14:47 4.19-rt and 5.10-rt should be on schedule. 12:17:12 4.19 regular is as well, it seems 12:17:19 5.10 12:17:38 same here 12:17:48 any other issues in sight? 12:18:11 Not on my side. 12:18:16 no issue 12:18:21 #topic Kernel testing 12:19:05 Hello 12:19:26 sent mail about isar-cip-core on kernelci https://github.com/kernelci/kernelci-core/pull/1656 12:19:38 to cip-dev 12:20:14 Thanks Arisu 12:20:59 about if we want to just move to bullseye or we want to keep also buster to be tested on kernelci 12:21:41 In the gitlab setup, it depends on which kernel version is used 12:21:57 To map with how Debian does it I believe 12:22:10 Do we want to do something similar in kernelci? 12:22:23 yeah, likely to avoid surprises in userland 12:22:24 Older kernels - buster. Newer - bullseye 12:22:31 exactly 12:23:16 how much older kernel? 12:23:36 4.19? 4.4? 12:23:43 4.4 would likely be better done with buster, though it should work with bullseye as well 12:24:15 Arisu: I need to check 12:24:16 doing 4.4 with bookworm one day could be risky, if possibly at all 12:24:36 ok thanks. 12:26:05 anything else on testing? 12:26:25 I don't have anything special this week 12:26:50 nothing else 12:27:06 then move on in... 12:27:10 3 12:27:12 2 12:27:14 1 12:27:16 #topic AOB 12:27:46 anything else for today? 12:28:05 Should we do some next steps with 6.1-cip? 12:28:48 what would be next now? 12:29:46 Big announcement that 6.1-cip is happening, starting branch, start requiring all the patches for 5.10 be submitted for 6.1....? 12:30:06 Sounds about right 12:30:33 so, branch should be created IMHO 12:30:34 and decide reference HW for 6.1-cip. 12:30:41 ack 12:31:29 Did we already do the decision that 6.1-cip is happening? 12:31:45 we decided to start the development, yes 12:32:01 we didn't decide to do a first release tomorrow already 12:32:32 so, get everything ready that we could accept patches and could do releases the other day 12:32:53 which includes the points above 12:34:18 Ok, so let me summarize what needs to be done and send it as a comment to the list...? 12:34:46 +1 12:36:12 other topics? 12:36:36 It would be helpful if you could do it. 12:38:13 if nothing else, closing in... 12:38:16 3 12:38:18 2 12:38:20 1 12:38:22 #endmeeting