13:00:37 <jki> #startmeeting CIP IRC weekly meeting
13:00:37 <collab-meetbot> Meeting started Thu Apr 10 13:00:37 2025 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:37 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:37 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:00:50 <jki> #topic AI review
13:00:59 <jki> - share release scripts/procedures [iwamatsu-san]
13:01:06 <jki> I think this is done now
13:01:25 <jki> I should have stated "discuss how to re-use things"...
13:01:46 <jki> we can do under AOB
13:02:03 <jki> - ask for adjusting reply-to setting on CIP MLs [jan]
13:02:11 <jki> done, changes should be effective
13:02:18 <jki> can someone confirm this?
13:03:05 <jki> pavel: you asked for it
13:03:40 <pave1> yep. I guess mark this as done
13:03:41 <patersonc> If I "reply" to an email sent to cip-dev the reply address is now the original sender not the ML
13:03:58 <patersonc> So it's working
13:04:07 <pave1> and I'll verify it over the week.
13:04:10 <jki> reply-to-all is what you should always use on lists ;)
13:04:16 <jki> good
13:04:28 <jki> any other AIs?
13:04:30 <patersonc> reply-to-all also does as expected
13:04:54 <jki> 5
13:04:55 <jki> 4
13:04:57 <jki> 3
13:04:59 <jki> 2
13:05:01 <jki> 1
13:05:02 <jki> #topic Kernel maintenance updates
13:05:18 <masami> This week reported 23 new CVEs and 6 updated CVEs.
13:05:19 <pave1> I was reviewing 6.1.133 and .134
13:05:23 <uli_> working on 4.4
13:05:49 <iwamatsu__> I reviewed 6.1.133, and reviewing .132
13:07:41 <jki> anything else?
13:07:57 <jki> 5
13:07:59 <jki> 4
13:08:00 <jki> 3
13:08:02 <jki> 2
13:08:04 <jki> 1
13:08:05 <jki> #topic Kernel release status
13:08:13 <jki> all lights are green
13:08:33 <jki> any issues ahead?
13:09:18 <jki> if not
13:09:20 <pave1> not really. 6.1-rt releases are now more than 4 weeks apart
13:09:21 <jki> 5
13:09:38 <jki> do we know why?
13:09:39 <pave1> so we might want to use 6.12 tree as an excuse
13:09:56 <pave1> to do -cip-rt less often.
13:10:21 <pave1> No idea why. I guess maintainer workload.
13:10:41 <jki> I still want you to talk to them from time to time
13:10:53 <jki> not yet partiticpating in their meetups, right?
13:11:01 <jki> could be helpful...
13:11:15 <pave1> right, should do that I guess.
13:11:49 <jki> yes, please
13:12:12 <jki> ok, then let's move on
13:12:16 <jki> 5
13:12:18 <jki> 4
13:12:20 <jki> 3
13:12:22 <jki> 2
13:12:23 <jki> 1
13:12:25 <jki> #topic Kernel testing
13:12:47 <arisut> no updates from me, still working on moving the configurations to KernelCI
13:13:09 <patersonc> Nothing from me either
13:13:41 <jki> all test pipelines running smoothly?
13:14:14 <pave1> I do have to hit retry on gitlab, usually.
13:14:33 <pave1> plus 6.14 is out, would be nice to test it.
13:15:15 <jki> the retry need is new?
13:15:31 <patersonc> same issue as always
13:15:46 <pave1> no. that's long-standing. but would not mind if it went away.
13:16:20 <jki> understandable
13:17:20 <jki> anyone with some cycles who could have a look?
13:19:02 <jki> seems not - maybe hit retry the other week on this ;)
13:19:12 <jki> anything else on testing?
13:19:24 <pave1> will retry in month or so :)
13:19:48 <jki> 5
13:19:49 <jki> 4
13:19:51 <jki> 3
13:19:53 <jki> 2
13:19:54 <jki> 1
13:19:56 <jki> #topic AOB
13:20:11 <jki> two topics on my list
13:20:25 <jki> release scripting consolidation - where are we?
13:20:48 <pave1> I need to take a look at Iwamatsu-san's scripts.
13:20:59 <jki> then you just gained an AI ;)
13:21:01 <jki> ok
13:21:13 <pave1> :-)
13:21:22 <jki> uli_: you already picked something up, or what was the status?
13:21:30 <iwamatsu__> pave1: if you have a issue and question, please let me know.
13:21:47 <uli_> i use the scripts in lts-commit-list
13:21:55 <uli_> that's pretty much it
13:22:10 <jki> cool
13:22:31 <jki> good, then let's revisit after pavel had a look as well
13:22:57 <jki> second topic: 6.12-cip release, roadmap and preconditions
13:23:35 <pave1> testing seems ok, we are already taking patches to 6.1 and 6.12
13:24:35 <jki> given that we have patches in 6.12-cip, a release would be justified, I guess
13:24:48 <jki> anything missing for that?
13:24:51 <pave1> configs should be confirmed by the members, wiki page update
13:25:05 <jki> do we need to discuss release cadences for 6.1?
13:25:17 <jki> right, configs...
13:25:58 <jki> and https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware
13:25:58 <iwamatsu__> about configs, I got mail from renesas.
13:26:14 <pave1> and yes, it seems to be rigght time to reduce 6.1 cadence :-)
13:26:17 <jki> but reference hw can start small, then grow
13:27:08 <pave1> and decide who is responsible for tree and releases.
13:27:49 <jki> 6.12-rt topic is also to finalize then
13:28:00 <jki> we still have no real feedback for that, I guess
13:28:11 <jki> arm32 support, sched lazy...
13:28:36 <pave1> I'd say no 6.12-rt tree and see what happens.
13:29:02 <jki> so, ask interested members to propose missing RT features for backport?
13:29:10 <pave1> yes.
13:29:44 <jki> then let me summerize what should be proposed/discussed during next TSC:
13:30:06 <jki> - reference boards (qemu is set - what else?)
13:30:17 <jki> - confirm / propose configs for 6.12
13:30:49 <jki> - reduce release cadence of 6.1 to 1 (vanilla) and 0.5 (rt) per month?
13:31:21 <jki> - no rt tree, members should propose missing RT features as backports to 6.12-cip
13:31:27 <jki> anything else?
13:31:46 <pave1> - confirm cadence of 6.12 twice a month
13:32:01 <jki> good point
13:32:22 <pave1> - decide who is responsible for tree and releases (tsc or here)
13:32:22 <jki> ah: maintainer will be....
13:32:34 <jki> that is something we as kernel WG need to tell
13:33:11 <jki> iwamatsu__: would you have the capacity for that?
13:33:47 <iwamatsu__> Probably okay.
13:34:15 <jki> we can always rearrange things if they do not work anymore
13:34:22 <pave1> so model stays them as 6.1, with me + iwamatsu-san maintaining the tree
13:34:37 <pave1> and mostly iwamatsu-san doing the releases?
13:35:53 <iwamatsu__> Yes, that's fine.
13:35:58 <iwamatsu__> to me
13:36:06 <pave1> fine with me, too.
13:36:36 <jki> pavel: I suspect your efforts will go up as well, even if there is not dedicated 6.12-rt
13:36:54 <jki> with 4.4 and 4.19-rt self-maintained
13:37:25 <pave1> yep.
13:37:28 <jki> plus potential rt backports to 6.12 if we take extras there
13:37:30 <jki> ok
13:37:52 <jki> then we have a rough plan and some food for discussion at the next TSC
13:38:02 <pave1> +1
13:38:23 <iwamatsu__> +1
13:38:43 <jki> any other topics for today?
13:39:47 <jki> 5
13:39:49 <jki> 4
13:39:51 <jki> 3
13:39:53 <jki> 2
13:39:56 <jki> 1
13:40:04 <jki> #endmeeting