13:01:59 <jki> #startmeeting CIP IRC weekly meeting
13:01:59 <collab-meetbot> Meeting started Thu Dec  5 13:01:59 2024 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:01:59 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:01:59 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:05 <jki> #topic AI review
13:02:09 <jki> - prepare blog entry on SLTS kernel state and challenges [Jan]
13:02:33 <jki> once again, /me was very busy with other stuff :(
13:02:45 <jki> hope to get it done before x-max :)
13:03:03 <jki> I'm not seeing other AIs from last week, so...
13:03:08 <jki> 5
13:03:09 <jki> 4
13:03:11 <jki> 3
13:03:12 <jki> 2
13:03:13 <jki> 1
13:03:14 <jki> #topic Kernel maintenance updates
13:03:48 <masami> This week reported 38 new CVEs and 0 updated CVEs.
13:03:54 <pave1> New kernel release cycle began, so 6.1.120 is going to be huge. Reviewing that.
13:04:12 <pave1> (And leftovers from the last cycle).
13:04:19 <uli_> i pushed out 4.4
13:04:52 <iwamatsu__> I reviewed 6.1.118 and 119.
13:06:19 <jki> anything else?
13:06:43 <patersonc> I see that 6.12 is now listed on https://www.kernel.org/category/releases.html
13:06:56 <pave1> There were questions about that on TSC.
13:07:33 <jki> oh, missed that, thanks for the hint
13:07:37 <pave1> Hmm. Fun, it is marked as longterm on that page, but not on main page.
13:07:38 <jki> was there anything on some list?
13:08:02 * patersonc shrugs
13:08:08 <jki> err, 6.12 is not listed on that page yet
13:08:19 <jki> latest version is still 6.6
13:08:33 <patersonc> Cache?
13:08:38 <patersonc> https://usercontent.irccloud-cdn.com/file/cN4DiqPN/image.png
13:08:59 <pave1> Aha, no;
13:09:04 <pave1> https://www.kernel.org/category/releases.html is confusing
13:09:10 <jki> indeed, just open again in a private tab
13:09:19 <jki> now it's there, updated today
13:09:32 <pave1> Says 'Longterm release kernels' but then lists two years ...
13:10:02 <jki> longer than 2 months ;)
13:10:51 <patersonc> LTS support usually starts at 2 years, then is increased as time goes on if there's enough interest/support etc.
13:11:40 <pave1> Yup, right. But 5.10 + 6.1 + 6.12 all ending on Dec 2026 looks really, really scary.
13:11:57 <jki> well, but none of that is any news
13:12:36 <pave1> And I thought 2025 would be bad :)
13:13:04 <jki> good news: it won't get worse after that ;)
13:13:45 <jki> but, yes, we will gain 3 new self-maintained kernels at once in 2027
13:14:26 <patersonc> My current understanding is that most LTSs will end up being supported for 4 years
13:14:33 <jki> and drop one at that time (4.4)
13:14:57 <jki> where was that 4 years thing communicated?
13:15:13 <pave1> My understanding was similar to patersonc's.
13:17:07 <jki> ?
13:18:54 <pave1> No idea. Patersonc?
13:19:11 <patersonc> Greg told me :)
13:20:22 <jki> well, we will see
13:20:50 <jki> anyway - still the question where we should place our announcement outside of cip-dev
13:20:56 <jki> if there is no email thread yet
13:21:11 <jki> if someone spots something, let me know
13:21:14 <pave1> Ok.
13:21:23 <pave1> Also, there'll be last 4.19.X release.
13:21:39 <pave1> I guess that's good place to announce we'll be continuing to maintain this.
13:22:11 <jki> yes, that would be good for 4.19
13:22:30 <jki> but for 6.12, I will probably start an own thread somewhere next week, cip-dev/lkml/stable
13:22:42 <pave1> 4.19 -- Should I do that?
13:23:35 <jki> pavel: yes, sure
13:23:39 <pave1> ok.
13:23:59 <jki> maybe we should just cooardinate so that we can cross-reference threads
13:24:31 <pave1> ok, so you cc me and I cc you, so that the second post can cross-reference?
13:24:49 <jki> do we have an idea when that final 4.19 will be?
13:25:24 <pave1> jki: I'd expect it in few days, no more than a week.
13:25:58 <jki> that sounds good
13:26:50 <jki> ok - anything else?
13:26:59 <jki> 5
13:27:01 <jki> 4
13:27:03 <jki> 3
13:27:05 <jki> 2
13:27:07 <jki> 1
13:27:10 <jki> #topic Kernel release status
13:27:24 <jki> 4.4 and 4.19 rt are late
13:27:28 <pave1> 4.4-rt late, sorry about that.
13:27:46 <pave1> 4.19-rt: I asked for an update, -rc1 is more than week old, so I expect we get that.
13:28:18 <jki> ok, then there is hope :)
13:28:41 <pave1> 6.1-rt: 6.1.119-rt is out. I gues I'll do matching -cip and then -cip-rt, unless someone objects.
13:29:13 <jki> sounds good
13:29:18 <pave1> (y)
13:30:13 <jki> moving on...
13:30:15 <jki> 5
13:30:17 <jki> 4
13:30:18 <jki> 3
13:30:20 <jki> 2
13:30:22 <jki> 1
13:30:24 <jki> #topic Kernel testing
13:30:56 <patersonc> Howdy. I've not been up to much this week I'm afraid
13:31:28 <pave1> bbb is still acting up. I had to retry 6.11.X maybe 10 times.
13:31:59 <patersonc> still... Sorry Pavel
13:33:52 <jki> more testing topics?
13:34:51 <jki> maybe one from my side:
13:35:16 <jki> there are requests (one public) to add Raspberry Pi 4 to our target set, at least inofficially
13:35:32 <jki> does anyone else see value or has concerns?
13:35:54 <pave1> We should probably do that.
13:36:05 <pave1> It is slightly unusual hardware, but it is cheap and common.
13:36:14 <jki> exactly
13:36:30 <jki> should work for 6.1, otherwise 6.12 for sure
13:36:39 <jki> upstream, obviously
13:36:44 <iwamatsu__> +1
13:36:52 <patersonc> Any particular reason to use Pi4 over the other versions?
13:37:01 <jki> I will put that on the agenda for next TSC
13:37:08 <jki> RPi4 is legacy
13:37:24 <pave1> RPi3 is too old, RPi5 is too new :-).
13:37:25 <jki> RPi5 is - to my knowledge - not yet sufficently upstream
13:37:47 <patersonc> Fair doos :)
13:38:05 <jki> perfect
13:38:19 <jki> anything else?
13:38:33 <jki> 5
13:38:35 <jki> 4
13:38:38 <jki> 3
13:38:40 <jki> 2
13:38:42 <jki> 1
13:38:44 <jki> #topic AOB
13:39:03 <jki> other topics for today?
13:39:49 <jki> 5
13:39:51 <jki> 4
13:39:52 <jki> 3
13:39:54 <jki> 2
13:39:56 <jki> 1
13:39:58 <jki> #endmeeting