13:01:04 <jki_> #startmeeting CIP IRC weekly meeting 13:01:04 <collab-meetbot`> Meeting started Thu May 8 13:01:04 2025 UTC and is due to finish in 60 minutes. The chair is jki_. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:01:04 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:04 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting' 13:01:15 <jki_> #topic AI review 13:01:26 <jki_> o- write docs for release scripts [iwamatsu-san] 13:01:55 <iwamatsu__> I updated README. 13:02:22 <jki_> hmm, pavel not here, maybe inform him via email 13:02:25 <jki_> thanks! 13:02:37 <jki_> no other AIs recorded 13:02:46 <jki_> 5 13:02:48 <jki_> 4 13:02:48 <iwamatsu__> pave1: If you have a issue, please create a issue in gitlab.. 13:02:59 <jki_> 3 13:03:01 <jki_> 2 13:03:03 <jki_> 1 13:03:05 <jki_> #topic Kernel maintenance updates 13:03:25 <pave1> i'm here, sorry for being late. 13:03:30 <masami> This week reported 345 new CVEs and 78 updated CVEs. 13:03:31 <uli_> i pushed 4.19 today, going to do 4.4 next 13:04:04 <pave1> I was doing some reviews, 6.1.135+. 13:04:24 <iwamatsu__> I reviewed 6.1.133 and 134. And I have prepared a release of 6.1.y-cip. The release is scheduled for tomorrow. 13:05:38 <iwamatsu__> sorry , not 133 and 134. 6.1.235. 13:05:49 <iwamatsu__> s/235/135/ 13:06:43 <jki_> ok - anything to add? 13:07:10 <jki_> 5 13:07:12 <jki_> 4 13:07:14 <jki_> 3 13:07:16 <jki_> 2 13:07:18 <jki_> 1 13:07:20 <jki_> #topic Kernel release status 13:07:32 <jki_> 4.19 was late, now released 13:07:38 <jki_> 6.1 scheduled 13:07:44 <jki_> rest on track, right? 13:08:33 <jki_> how about 6.12? 13:09:24 <pave1> I guess we should do that. 13:10:05 <pave1> I believe first step would be to branch 13:10:36 <pave1> -rebase from current git state and release that as -cip1. 13:11:15 <patersonc> Do we want to fix the commit authors and force-push first? 13:11:27 <patersonc> I see there are some "Lad Prabhakar via lists.cip-project.org" authors 13:11:37 <jki_> if we are rebasing already, sure 13:11:56 <jki_> maybe deploy some merging scripts that check that in the future 13:12:16 <jki_> but do we need to rebase otherwise? 13:12:23 <pave1> We would not rebase otherwise. 13:12:32 <jki_> it's not really best style for production branches 13:12:37 <jki_> even if not yet tagged 13:13:10 <patersonc> Sure 13:13:26 <patersonc> It's a shame we've ended up with commits like that. It's not just the 6.12 branch either 13:14:37 <pave1> Sorry about that. 13:14:57 <patersonc> No worries 13:15:16 <jki_> that's why I'm asking for tools 13:15:33 <jki_> I have one here as well, but I'm doing single-patch merges only 13:16:33 <jki_> iwamatsu__: what's your view on the 6.12 state? 13:17:15 <iwamatsu__> It is good to me. I think we can release -cip1. 13:20:07 <jki_> greate 13:20:19 <jki_> up to you to schedule this, of course 13:20:27 <jki_> anything else to add? 13:20:38 <jki_> 5 13:20:38 <patersonc> FYI, current KernelCI test results for CIP 6.12: https://dashboard.kernelci.org/tree/6abf3600783c94555934f98e5c2fb8fa449f53b3?i=11&ti%7Cc=v6.12.19-79-g6abf3600783c&ti%7Cch=6abf3600783c94555934f98e5c2fb8fa449f53b3&ti%7Cgb=linux-6.12.y-cip&ti%7Cgu=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fcip%2Flinux-cip.git&ti%7Ct=cip 13:21:18 <jki_> 4 13:21:20 <jki_> 3 13:21:22 <jki_> 2 13:21:23 <jki_> 1 13:21:25 <jki_> #topic Kernel testing 13:21:48 <arisut> working with kernelci on restoring the cip fragments configurations 13:22:21 <arisut> currently we are testing on 6.1 cip as looks like is still using cip fragments on kernelci 13:22:55 <patersonc> KernelCI is now only testing the ARCH we care about 13:23:28 <arisut> I'm also looking into blocking not needed configurations 13:24:14 <arisut> like the cros fragments 13:26:02 <jki_> ok 13:26:28 <jki_> more on testing? 13:26:47 <patersonc> Not from me 13:27:48 <jki_> 5 13:27:51 <jki_> 4 13:27:54 <jki_> 3 13:27:56 <jki_> 2 13:27:57 <jki_> 1 13:27:59 <jki_> #topic AOB 13:29:12 <jki_> anything else? 13:29:32 <jki_> 5 13:29:34 <jki_> 4 13:29:37 <jki_> 3 13:29:39 <jki_> 2 13:29:41 <jki_> 1 13:29:45 <jki_> #endmeeting