13:02:44 <jki> #startmeeting CIP IRC weekly meeting
13:02:44 <collab-meetbot> Meeting started Thu Nov  9 13:02:44 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:02:44 <collab-meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:02:44 <collab-meetbot> The meeting name has been set to 'cip_irc_weekly_meeting'
13:02:53 <jki> #topic AI review
13:03:01 <jki> nothing on the list
13:03:17 <hunter> what exactly is the focus for AI in this context?
13:03:24 <jki> Action Items
13:03:41 <hunter> ahhh ok
13:04:00 <jki> well, helping you with getting onboarded would be been one
13:04:26 <jki> hope that worked without formal tracking ;)
13:05:00 <jki> if I didn't forget more - moving on...
13:05:03 <jki> 5
13:05:06 <jki> 4
13:05:08 <jki> 3
13:05:10 <jki> 2
13:05:11 <jki> 1
13:05:13 <jki> #topic Kernel maintenance updates
13:05:25 <pave1> Reviewing 6.1.62. Otherwise it is reasonably quiet.
13:05:30 <masami> This week reported 1 new CVEs and 7 updated CVEs.
13:05:36 <uli> prepped 4.4 for release
13:06:07 <iwamatsu> I reviewed 6.1.62. And I am preparing to release linux-5.10.y-cip with 5.10.200.
13:07:54 <jki> anything else?
13:08:27 <pave1> Mainline is in -rc phase, so -stable is quiet now.
13:08:50 <jki> mainline is about to enter -rc
13:09:05 <jki> btw it looks like -rt could make it this cycle
13:09:18 <jki> printk changes should have been completed
13:09:24 <pave1> I meant "-rc1" phase.
13:09:56 <pave1> Well, there will be always long tail of rt changes. But yes, I guess that's a bit of milestone.
13:10:43 <jki> any other updates?
13:10:50 <jki> 5
13:10:52 <jki> 4
13:10:53 <jki> 3
13:10:55 <jki> 2
13:10:56 <jki> 1
13:10:59 <jki> #topic Kernel release status
13:11:04 <jki> 4.4
13:11:08 <uli> 4.4-cip81 and 4.4-st46 are out
13:11:18 <jki> great
13:11:38 <pave1> 4.4-rt is on track.
13:11:46 <jki> 4.19
13:12:16 <pave1> 4.19/5.10/6.1-rt is on track.
13:12:16 <iwamatsu> on track.
13:12:28 <pave1> 5.10-rt is next due, in 10 days.
13:12:43 <jki> - 5.10
13:12:52 <jki> to appear, as we just learned
13:13:10 <jki> and 6.1
13:13:25 <iwamatsu> on track.
13:13:42 <jki> good
13:13:48 <jki> #topic Kernel testing
13:14:45 <jki> not much apparently - without Chris
13:15:03 <sietze> Chris and I had a meeting today
13:15:04 <arisut> not much from me
13:15:16 <hunter> I am working on the weekly output for results tomorrow.
13:15:29 <hunter> as in sending it
13:15:39 <jki> hunter: cool!
13:16:10 <jki> sietze: anything to share from that meeting?
13:16:13 <sietze> Chris and I are working on hooking up SQUAD to the actual kernel tests
13:16:54 <sietze> I also will be adding some diagrams to the wiki and rtd documentation
13:17:10 <sietze> On the testing framework
13:18:17 <jki> also great!
13:18:37 <sietze> And we discussed briefly, how SQUAD could serve as an information source maybe for Hunter's reports
13:18:49 <sietze> But we really need a dedicated meeting for that I guess
13:18:51 <jki> that was my first thought as well!
13:19:09 <hunter> sounds like a plan
13:19:20 <jki> zoom call? or irc round?
13:19:40 <sietze> Chris and I use Teams, since our companies provide that
13:19:46 <sietze> But we're flexible
13:19:49 <sietze> :-)
13:19:58 <hunter> Teams or IRC is okay : ]
13:20:24 <sietze> Then let's pick teams I propose
13:20:32 <hunter> Sounds good to me.
13:21:00 <jki> great!
13:21:23 <jki> more on testing for today?
13:21:41 <sietze> that was it from side
13:21:50 <sietze> my side
13:22:12 <jki> then moving on...
13:22:14 <jki> 5
13:22:16 <jki> 4
13:22:17 <jki> 3
13:22:19 <jki> 2
13:22:20 <jki> 1
13:22:22 <jki> #topic AOB
13:23:36 <jki> release delay guidelines:
13:23:44 <jki> we had now some delay of 5.10 due to a regression on one reference board
13:24:07 <jki> I was wondering if we should clarify how long to wait at max
13:24:40 <jki> and when to maybe document, release, and rather follow up with fix later
13:24:54 <jki> thoughts?
13:25:21 <pave1> I believe this was rather exceptional case. I don't believe we need to decide/document anything at the moment.
13:26:04 <jki> but still: why wait for one board when the rest is not affected?
13:26:19 <jki> why didn't we revert in this case?
13:26:48 <pave1> We could have.
13:27:08 <pave1> But then you'll get revert and then reapply on the rebase branch.
13:27:28 <pave1> so waiting seemed like better solution to me.
13:28:10 <pave1> We could also do release based on 5.10.198 -- that's before the regression.
13:28:47 <iwamatsu> Users don't know why the release is delayed, so some kind of announcement may be necessary.
13:29:48 <iwamatsu> That's a problem with my release work...
13:30:51 <jki> no criticism - and I also heard no complaints
13:31:02 <jki> just wanted to understand and make us reflect
13:32:36 <jki> good - anything else?
13:33:16 <jki> 5
13:33:18 <jki> 3
13:33:21 <jki> 4
13:33:23 <jki> 2
13:33:24 <jki> 1
13:33:27 <jki> #endmeeting