12:02:37 <jki> #startmeeting CIP IRC weekly meeting 12:02:37 <collab-meetbot> Meeting started Thu Jun 15 12:02:37 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:37 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:02:37 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting' 12:02:42 <jki> #topic AI review 12:02:46 <jki> 1. create kernelci pipeline for buster images (arisut) 12:03:23 <arisut> currently testing it 12:03:38 <jki> good 12:03:53 <jki> any other AI? 12:04:18 <jki> 3 12:04:20 <jki> 2 12:04:21 <jki> 1 12:04:23 <jki> #topic Kernel maintenance updates 12:04:44 <uli> i'm reviewing 6.1.34 12:04:47 <masami> This week reported 4 new CVEs and 7 updated CVEs. 12:05:34 <iwamatsu> I am reviewing 6.1.33 and 34. 12:07:52 <jki> anything else? 12:08:54 <jki> 3 12:08:56 <jki> 2 12:08:58 <jki> 1 12:08:59 <jki> #topic Kernel release status 12:09:03 <jki> -4.4 12:09:07 <uli> on track 12:09:23 <pave1> Reviews -- 6.1.34 and Renesas patches. 12:09:40 <pave1> (Sorry, bad connection) 12:09:47 <jki> np 12:09:50 <jki> -4.19 12:09:51 <pave1> 4.4-rt should be on track, too. 12:10:31 <pave1> 4.19-rt -- did one early, because last one was based on old -rt version. 12:11:17 <jki> 5.10 12:12:00 <iwamatsu> 5.10-rt is delayed. 12:12:26 <iwamatsu> about 1 week. 12:12:26 <jki> because of LTS-rt? 12:12:49 <pave1> I believe I seen -rt-rc, I can do release easily when we get matching versions. 12:13:17 <jki> would be good, thanks 12:13:50 <pave1> 6.1 12:13:58 <jki> yep 12:14:02 <pave1> I believe we should do release. 12:14:32 <pave1> Can we simply ask on memebers and get an approval there? 12:15:21 <jki> we can ask the members on Monday, 26th 12:15:25 <jki> during TSC 12:15:44 <pave1> I know that was a plan. 12:15:45 <jki> if everything is ready by then, we could set the tag later that day 12:16:06 <pave1> But Renesas is now submitting patches for 6.1 12:16:26 <jki> should they go in after a first release? 12:16:34 <pave1> and I believe it would be good to have a release before we get 12:16:40 <pave1> many more of those. 12:16:57 <patersonc[m]> pave1: We can pause submitting more patches if you prefer until cip1 is out 12:17:43 <pave1> petersonc> how many more do you have in the pipeline? 12:18:16 <patersonc[m]> Maybe not many, for a while a least 12:18:43 <pave1> So waiting until TSC is not a big deal. 12:18:50 <iwamatsu> +1 12:19:01 <jki> ok, then keep the plan 12:19:09 <patersonc[m]> (y) 12:19:10 <pave1> ok. 12:19:16 <jki> move on? 12:19:46 <pave1> We don't need to pause for few of them. 12:19:58 <pave1> ok. 12:20:10 <jki> #topic Kernel testing 12:20:51 <patersonc[m]> Hi 12:21:01 <arisut> no other updates from me other than the AI 12:21:39 <patersonc[m]> I had a meeting yesterday with someone from Linaro to learn more about SQUAD - potential front end/regression tracker to collate results from our testing (not just for Kernel, but also any CIP-Core testing etc.) 12:22:01 <patersonc[m]> I'll put together some thoughts/plans for the E-TSC in Prague 12:22:16 <jki> ah, cool 12:22:38 <arisut> nice 12:22:49 <patersonc[m]> That's it from me this week 12:23:02 <iwamatsu> nice 12:23:42 <patersonc[m]> No build issues with latest CIP 6.1 branch btw: https://linux.kernelci.org/build/cip/branch/linux-6.1.y-cip/kernel/v6.1.31-53-g486caac40d06/ 12:24:15 <arisut> as is using lava for getting results maybe we can get also from kernelci CIP jobs 12:24:49 <patersonc[m]> arisut: Yea that should be doable 12:27:19 <jki> anything else regarding testing? 12:27:43 <jki> 5 12:27:45 <jki> 4 12:27:46 <jki> 3 12:27:47 <jki> 2 12:27:49 <jki> 1 12:27:51 <jki> #topic AOB 12:29:55 <jki> anyone anything? 12:31:18 <jki> 3 12:31:20 <jki> 2 12:31:22 <jki> 1 12:31:24 <jki> #endmeeting