Thursday, 2023-11-09

« Wednesday, 2023-11-08 Index Friday, 2023-11-10 »
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:48
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:53
*** frieder <frieder!~frieder@i577B9007.versanet.de> has joined #cip07:55
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip08:28
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 252 seconds)10:15
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Ping timeout: 250 seconds)10:15
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip10:25
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip10:25
*** hunter <hunter!~hunter@dy584xqgw4cbnr2y88-kt-4.rev.dnainternet.fi> has joined #cip10:29
*** uli_ <uli_!~quassel@static.153.40.69.159.clients.your-server.de> has joined #cip11:30
*** uli_ is now known as uli11:31
hunterhello12:01
arisuthello12:02
patersoncAccording to Jan's email the meeting is in an hour btw (13:00 UTC). The channel header should probably be fixed12:08
hunterahh ok12:08
hunterwill wait until then12:08
patersonc:)12:09
patersoncI may have to miss it I'm afraid - I've got a clash this week. I'll try and chip in though if I can12:09
hunterit's no worries see you next thursday! have great weekend patersonc12:14
*** hunter <hunter!~hunter@dy584xqgw4cbnr2y88-kt-4.rev.dnainternet.fi> has quit IRC (Quit: Konversation terminated!)12:32
*** masami <masami!~masami@FL1-125-195-134-41.tky.mesh.ad.jp> has joined #cip12:51
arisutpatersonc: is from now on the time change ?12:59
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip13:00
pave1hi!13:00
sietzeHello!13:00
masamihello13:00
*** jki <jki!~jki@46.128.89.130> has joined #cip13:00
jkihi everyone13:00
ulihello13:00
iwamatsuhi13:01
*** hunter <hunter!~hunter@dy584xqgw4cbnr2y88-kt-4.rev.dnainternet.fi> has joined #cip13:01
arisuthi13:01
hunterhello13:01
jkiok, let's go13:02
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbotMeeting 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
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'13:02
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:02
jki#topic AI review13:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jkinothing on the list13:03
hunterwhat exactly is the focus for AI in this context?13:03
jkiAction Items13:03
hunterahhh ok13:03
*** hiromotai <hiromotai!~hiromotai@240f:75:5bc9:1:1c46:de70:27e4:fb7c> has joined #cip13:03
jkiwell, helping you with getting onboarded would be been one13:04
jkihope that worked without formal tracking ;)13:04
jkiif I didn't forget more - moving on...13:05
jki513:05
jki413:05
jki313:05
jki213:05
jki113:05
jki#topic Kernel maintenance updates13:05
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:05
pave1Reviewing 6.1.62. Otherwise it is reasonably quiet.13:05
masamiThis week reported 1 new CVEs and 7 updated CVEs.13:05
uliprepped 4.4 for release13:05
iwamatsuI reviewed 6.1.62. And I am preparing to release linux-5.10.y-cip with 5.10.200.13:06
jkianything else?13:07
pave1Mainline is in -rc phase, so -stable is quiet now.13:08
jkimainline is about to enter -rc13:08
jkibtw it looks like -rt could make it this cycle13:09
jkiprintk changes should have been completed13:09
pave1I meant "-rc1" phase.13:09
pave1Well, there will be always long tail of rt changes. But yes, I guess that's a bit of milestone.13:09
jkiany other updates?13:10
jki513:10
jki413:10
jki313:10
jki213:10
jki113:10
jki#topic Kernel release status13:10
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:10
jki4.413:11
uli4.4-cip81 and 4.4-st46 are out13:11
jkigreat13:11
pave14.4-rt is on track.13:11
jki4.1913:11
pave14.19/5.10/6.1-rt is on track.13:12
iwamatsuon track.13:12
pave15.10-rt is next due, in 10 days.13:12
jki- 5.1013:12
jkito appear, as we just learned13:12
jkiand 6.113:13
iwamatsuon track.13:13
jkigood13:13
jki#topic Kernel testing13:13
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:13
jkinot much apparently - without Chris13:14
sietzeChris and I had a meeting today13:15
arisutnot much from me13:15
hunterI am working on the weekly output for results tomorrow.13:15
hunteras in sending it13:15
jkihunter: cool!13:15
jkisietze: anything to share from that meeting?13:16
sietzeChris and I are working on hooking up SQUAD to the actual kernel tests13:16
sietzeI also will be adding some diagrams to the wiki and rtd documentation13:16
sietzeOn the testing framework13:17
jkialso great!13:18
sietzeAnd we discussed briefly, how SQUAD could serve as an information source maybe for Hunter's reports13:18
sietzeBut we really need a dedicated meeting for that I guess13:18
jkithat was my first thought as well!13:18
huntersounds like a plan13:19
jkizoom call? or irc round?13:19
sietzeChris and I use Teams, since our companies provide that13:19
sietzeBut we're flexible13:19
sietze:-)13:19
hunterTeams or IRC is okay : ]13:19
sietzeThen let's pick teams I propose13:20
hunterSounds good to me.13:20
jkigreat!13:21
jkimore on testing for today?13:21
sietzethat was it from side13:21
sietzemy side13:21
jkithen moving on...13:22
jki513:22
jki413:22
jki313:22
jki213:22
jki113:22
jki#topic AOB13:22
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:22
jkirelease delay guidelines:13:23
jkiwe had now some delay of 5.10 due to a regression on one reference board13:23
jkiI was wondering if we should clarify how long to wait at max13:24
jkiand when to maybe document, release, and rather follow up with fix later13:24
jkithoughts?13:24
pave1I believe this was rather exceptional case. I don't believe we need to decide/document anything at the moment.13:25
jkibut still: why wait for one board when the rest is not affected?13:26
jkiwhy didn't we revert in this case?13:26
pave1We could have.13:26
pave1But then you'll get revert and then reapply on the rebase branch.13:27
pave1so waiting seemed like better solution to me.13:27
pave1We could also do release based on 5.10.198 -- that's before the regression.13:28
iwamatsuUsers don't know why the release is delayed, so some kind of announcement may be necessary.13:28
iwamatsuThat's a problem with my release work...13:29
jkino criticism - and I also heard no complaints13:30
jkijust wanted to understand and make us reflect13:31
jkigood - anything else?13:32
jki513:33
jki313:33
jki413:33
jki213:33
jki113:33
jki#endmeeting13:33
collab-meetbotMeeting ended Thu Nov  9 13:33:27 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:33
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/11/cip.2023-11-09-13.02.html13:33
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/11/cip.2023-11-09-13.02.txt13:33
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/11/cip.2023-11-09-13.02.log.html13:33
*** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 12:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"13:33
jkithank you all!13:33
pave1Thank you!13:33
ulithanks13:33
masamithank you13:33
hunterthanks everyone!13:34
arisutthanks13:34
iwamatsuthank you13:34
*** hunter <hunter!~hunter@dy584xqgw4cbnr2y88-kt-4.rev.dnainternet.fi> has quit IRC (Quit: Konversation terminated!)13:34
*** jki <jki!~jki@46.128.89.130> has quit IRC (Quit: Leaving)13:34
*** hiromotai <hiromotai!~hiromotai@240f:75:5bc9:1:1c46:de70:27e4:fb7c> has quit IRC (Quit: Leaving)13:35
*** masami <masami!~masami@FL1-125-195-134-41.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:36
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving)15:28
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:41
*** frieder <frieder!~frieder@i577B9007.versanet.de> has quit IRC (Remote host closed the connection)16:50
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed)17:19
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip20:43
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has quit IRC (Quit: Client closed)22:07
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has quit IRC (Quit: Connection closed)22:07
*** prabhakar <prabhakar!~prabhakar@217.163.141.2> has joined #cip22:07
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.2> has joined #cip22:07
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 255 seconds)22:44
« Wednesday, 2023-11-08 Index Friday, 2023-11-10 »

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!