13:04:28 <jki> #startmeeting CIP IRC weekly meeting
13:04:28 <collab-meetbot`> Meeting started Thu Oct 24 13:04:28 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:04:28 <collab-meetbot`> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:04:28 <collab-meetbot`> The meeting name has been set to 'cip_irc_weekly_meeting'
13:04:32 <jki> #topic AI review
13:04:40 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:04:52 <jki> moved to the back again over vacation...
13:05:09 <jki> I haven't seen other AIs from last week, right?
13:05:18 <jki> 5
13:05:20 <jki> 4
13:05:22 <jki> 3
13:05:23 <jki> 2
13:05:24 <pave1> No new ai.
13:05:25 <jki> 1
13:05:26 <pave1> AIs.
13:05:29 <jki> #topic Kernel maintenance updates
13:05:46 <masami> This week reported 384 new CVEs and 37 updated CVEs.
13:05:50 <pave1> I'm reviewing 6.1.113 / 114.
13:05:58 <uli> i reviewed 6.1.113 and prepared 4.4
13:06:17 <iwamatsu__> I am reviewing 6.1.114
13:07:15 <jki> did we already clarify who is handling the next 4.4, under which conditions?
13:07:32 <pave1> Not really, this sounds like a good place.
13:07:56 <uli> looking at the timing, i think it might even be best to push it back until i come back from japan on nov 14 (it's due nov 9)
13:08:11 <pave1> I'd say that's best plan.
13:08:30 <jki> yes, if there is nothing surprisingly urgent showing up, that is fine
13:08:51 <jki> good, check-mark
13:09:03 <jki> anything else?
13:09:26 <jki> 5
13:09:27 <jki> 4
13:09:29 <jki> 3
13:09:30 <jki> 2
13:09:32 <jki> 1
13:09:34 <jki> #topic Kernel release status
13:09:41 <jki> all are green right now
13:09:52 <jki> anything to add?
13:10:07 <pave1> I thought ... 4.19-cip-rt is now.
13:10:21 <jki> uups, indeed
13:10:31 <jki> was color-blind
13:10:53 <jki> actually, not -rt, vanilla 4.19
13:11:08 <iwamatsu__> I will working it.
13:11:15 <iwamatsu__> I am working it.
13:11:24 <jki> ok, great
13:11:33 <pave1> We don't have corresponding 4.19-rt, so I guess its a bit more waiting and then asking for 4.19-rt.
13:11:49 <jki> limit date: Sat Nov 23 10:34:04 AM UTC 2024
13:11:53 <jki> that's for 4.19-rt
13:11:55 <jki> no?
13:12:21 <pave1> Oops, yes, you are right. I made mistake in my notes, will fix.
13:12:46 <jki> okay...
13:12:59 <jki> then let's move on
13:13:02 <jki> 5
13:13:04 <jki> 4
13:13:05 <jki> 3
13:13:07 <jki> 2
13:13:08 <jki> 1
13:13:10 <jki> #topic Kernel testing
13:13:17 <arisut> no updates from me
13:13:32 <jki> seems lava master if fine again, right?
13:13:50 <jki> currently no issues in testing?
13:14:20 <patersonc> Seems okay at the moment
13:14:29 <jki> great
13:14:41 <patersonc> touch wood
13:14:50 <jki> and no intruder had to be kicked out ;)
13:14:53 <patersonc> And I got the Renesas lab back online this morning
13:15:40 <jki> other testing topics?
13:15:50 <jki> 5
13:15:52 <jki> 4
13:15:54 <jki> 3
13:15:56 <jki> 2
13:15:59 <jki> 1
13:16:01 <jki> #topic AOB
13:16:15 <jki> next week is E-TSC, again
13:16:27 <jki> anything we should bring up as kernel WG?
13:16:59 <pave1> I can't think of anything.
13:17:30 <jki> effort planning 2025 - I'm sure we will be asked again
13:17:55 <pave1> beggining of 2025 will be hard, yes.
13:18:03 <jki> we are currently planning with same contractural efforts
13:18:29 <pave1> I don't expect to hit the contracted hours this year.
13:18:35 <pave1> That may change in 2025 I guess.
13:18:52 <jki> ok, that is important input
13:19:04 <jki> do you expect to overshoot in 25?
13:19:22 <pave1> No idea ATM, really. I'd expect that no.
13:19:49 <jki> we can still react over the year, to a certain degree
13:19:57 <pave1> We are currently doing a lot of -stable reviewing.
13:20:07 <jki> which is good
13:20:28 <jki> do you mean we would have to reduce that for the sake of "own" work?
13:20:40 <pave1> I guess that we can do less over the "surge" expected in 2025, without great consequences.
13:21:07 <pave1> I'm not sure if we'll have to reduce that,
13:21:07 <jki> well, we will start with the next CIP kernel, and that will see a lot of updates initially
13:21:25 <pave1> but I believe we can reduce that if needed.
13:21:25 <jki> and there will be the 4.19 take-over, right?
13:21:37 <pave1> Yes, 4.19 takeover and new kernel.
13:22:24 <jki> folks, you doing the real work, just tell me early enough when the load goes up too much
13:22:45 <pave1> Will do, but it is hard to estimate at the moment :-).
13:22:55 <jki> we don't want interruptions, we want time to be able to react
13:23:01 <jki> yes, understood
13:23:01 <iwamatsu__> OK
13:23:13 <pave1> Currently, there's time to review patches that are not affecting any known CIP config.
13:23:37 <pave1> That's first on the list ;-).
13:23:46 <jki> sure
13:24:23 <jki> other businesses for today?
13:24:37 <patersonc> I guess there's potential for a wider config list for CIP to maintain if requests by any new members to the project. But obviously that cannot be predicted/estimated at this point. But perhaps worth considering
13:25:03 <patersonc> s/requests/requested
13:25:43 <jki> right
13:26:23 <jki> but maybe we could also ask a potential new member for getting involved ;)
13:26:36 <patersonc> True!
13:26:37 <pave1> Right ;-).
13:26:50 <jki> ideally also on testing...
13:27:06 <patersonc> yep
13:27:12 <pave1> There's also possibility to ask for pruning of configs. We have udf/btrfs on, bunch of scsi, etc.
13:27:26 <jki> sure
13:28:21 <jki> anything else for today?
13:28:31 <jki> 5
13:28:33 <jki> 4
13:28:35 <jki> 3
13:28:37 <jki> 2
13:28:38 <pave1> oh.
13:28:42 <jki> yes?
13:28:47 <pave1> E-tsc. That's like 4 am utc, right
13:28:48 <pave1> ?
13:29:00 <patersonc> Something like that
13:29:01 <jki> yes, but I will not be up that early as well
13:29:15 <pave1> So, no big deal if I can't make it? :-)
13:29:24 <jki> I hope Yoshi is not scheduling the kernel into our night
13:29:26 <patersonc> We can move the kernel team bit to the end?
13:29:34 <jki> yes, please
13:30:03 <jki> 6 am should work
13:30:36 <jki> maybe even 5 - we have the time shift next weekend
13:31:03 <patersonc> I'll make sure it's at the end during the meeting, or we can ask before hand if Yoshi-san publishes an agenda (I haven't seen one yet)
13:31:19 <jki> yep, thanks
13:31:59 <jki> ok... let's try closing again
13:32:02 <jki> 5
13:32:04 <jki> 4
13:32:06 <jki> 3
13:32:07 <jki> 2
13:32:09 <jki> 1
13:32:11 <jki> #endmeeting