IRC logs for #cip for Thursday, 2022-02-03

« Wednesday, 2022-02-02 Index Friday, 2022-02-04 »
*** rajm-and <rajm-and!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip07:24
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has joined #cip08:30
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has joined #cip08:37
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has joined #cip08:39
*** uli <uli!~uli@55d466c9.access.ecotel.net> has joined #cip12:18
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has joined #cip12:45
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has joined #cip12:59
iwamatsuping13:03
alicefpong13:04
iwamatsuhi13:04
iwamatsunot start yet?13:04
alicefhi o/13:04
aliceflooks like so13:04
alicefthere is also paterson but looks like matrix cannot connect here13:05
*** jki <jki!~jki@165.225.27.1> has joined #cip13:06
jki#startmeeting13:06
brloggerjki: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'13:06
alicefmlooks like this chat got disconnected from irc13:06
iwamatsuhmm13:06
jkihi all13:06
alicefmyes not sure why13:06
iwamatsuhi!13:06
masamihi13:07
jkialready started?13:07
alicefnot yet13:07
iwamatsuno, we were waiting13:07
jkiok, one moment - sorry13:07
jki#startmeeting CIP IRC weekly meeting13:08
brloggerMeeting started Thu Feb  3 13:08:08 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:08
brloggerUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:08
brloggerThe meeting name has been set to 'cip_irc_weekly_meeting'13:08
*** brlogger changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:08
jkihere we go13:08
jkifound the magic spell13:08
jkiwho is around?13:08
ulio/13:09
*** patersonc <patersonc!~patersonc@host86-168-176-9.range86-168.btcentralplus.com> has joined #cip13:09
iwamatsuhi13:09
masamihi13:09
josiahHi13:09
alicefjki: https://gist.github.com/aliceinwire/2e6320fe4cd12a128102ce6ee3d3724d13:09
alicefHi13:09
jkialicef: I have this as well, but when you are in hectic... ;)13:10
alicefthere is also patersonc but looks he have problems with matrix/element13:10
patersonchi13:10
patersoncJoining from another client now13:10
jkimissing pavel13:10
jkibut given that we are late already...13:10
jki#topic AI review13:10
*** brlogger changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:10
jki1. Request private KernelCI branches for CIP maintainers - patersonc13:11
jkiany news on this PR?13:11
patersoncFinally made the initial PR13:11
patersonchttps://github.com/kernelci/kernelci-core/pull/102213:11
patersoncSorry for the delay13:11
jkialicef: you will review this?13:12
alicefyes13:12
jkianything else missing for a merge?13:13
alicefI have already reviewed with patersonc in private13:13
alicefthe discussion was about enabling rc to be tested for each commit and not only tags13:14
alicefI don't think the PR is completely satisfy the issue request but is a good starting point13:15
patersoncAny push to the *-rc branches will be run in KernelCI13:15
patersoncJust maybe not instantly13:16
alicefoh nice you could confirm that?13:16
patersoncnot until it's merged, or manually triggered in staging13:17
alicefok thanks13:18
alicefI have no other objections13:19
alicefas now13:19
jkiok - so alicef will ack, and then someone else still needs to merge it, right?13:20
alicefusing cip_variants as I said looks good for me13:20
alicefack, staging test and merge13:21
jkigreat13:21
jkinext topic?13:21
alicefwe need also gtucker ack13:21
alicefyes next topic13:21
jki2. Make TSC motion regarding linux-4.4.y branch by CIP - jan13:22
jkithis has been sent13:22
jkiwas the wording ok for all?13:22
patersoncI think for the v4.4.y branch (non-cip) we should say we'll follow the current stable rules, not CIP's rules13:23
iwamatsuThat mean that we do not accept backports about features?13:24
jkiyes, regarding what CIP would additionally accept13:24
jkithat goes into cip only13:24
jkibut what we do not accept - because of out of scope - will also not go into 4.4.y13:25
jkithat was my idea behind referring to CIP rules13:25
patersoncv4.4.y = bug/security fixes (like current LTS). v4.4.y-cip = v4.4.y + feature backports (current SLTS rules)13:25
patersoncGotcha13:25
iwamatsuI understood.13:26
patersoncAgree that v4.4.y should be CIP scope only, just follow LTS rules13:26
jkiwe likely need to craft the announcement email carefully in this regard13:26
alicefmif someone send a pull request for out the cip scope will not be accepted?13:26
alicefmI'm understanding correctly?13:27
jkiat least we do not commit on accepting that - I would leave us the freedom to do so if there is value for us13:27
alicefmok13:28
jkiit's that thin line we were discussion last week and also in the TSC call13:28
jkimeanwhile, my motion still needs a second in order to start the actual voting13:28
jkior suggestions to sharping the wording13:28
jkianything else on this topic?13:30
alicefmwording looks ok from what i remember13:30
jki3. Draft press announcement about 5.10 release and 4.4 self-maintenance - jan13:31
jkii won this task during the TSC call13:31
jkididn't have time to look into it yet, though13:32
jkianything else for AIs?13:32
jki313:33
jki213:33
jki113:33
jki#topic Kernel maintenance updates13:33
*** brlogger changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:33
ulireviewed more 5.10.94 patches13:33
iwamatsuI reivewed 5.10.96.13:34
masamiThere was 8 new CVEs this week. also, there were tons of security fix for 4.X series.13:34
masamiI'll more look into security fix for 4.4.y from next week.13:37
masamimaybe, I'll send a patch to cip-dev mailing list if I can backport it.13:37
jkiwhat will be our criteria to look at backport candidates?13:38
jkiCVE attached? Or more?13:38
iwamatsuI also take a look.13:38
iwamatsuFor CVE, if it is  related to our reference board, try backport.13:39
jkiand how will we track that? our wiki is not tracking 4.9 and 4.14, only 4.19 regarding commits, thus backport candidates13:41
jkibtw, https://www.kernel.org/category/releases.html no longer lists 4.4 - was something sent already?13:41
iwamatsuI think other backports will be the same.13:42
iwamatsuCertainly we need a mechanism to manage patches  for 4.4.y.13:42
iwamatsu4.4.302 has been released.13:43
jkiah, ok13:43
iwamatsuit has EOL mark.13:43
jkijust today13:43
iwamatsuyes13:43
jkioh, Greg mentioned us13:44
jkiwe have the ball in our field13:44
jkibecause of "is considering" - we are decided to13:44
jkiI think we should probably move forward with Pavel's proposal soon then, not yet referring to the ongoing 4.4.y continuation thing13:46
jkithat could still be announced later on top, once we have the ok13:46
jkiI can follow up on Pavel's post to cip-dev, suggesting that13:47
patersoncHow often will CIP add to their own version of 4.4.y?13:48
patersoncAnd will there be "releases"?13:48
patersonc4.4.303 etc.?13:48
jkigood questions13:51
jkiit would probably make sense and should be easy to implement tagging releases along the CIP ones13:52
iwamatsuI do not know the release of releases now. if the patch is accumulated, it will be release...13:52
jkiI think this would be about tagging the baseline of 4.4.30X-cip with 4.4.30X, like before13:56
jkibut only in our continuation branch13:57
jkianyway, we need the general OK to publish and annouce the branch at all first13:57
jkiother topic here?13:57
jkitopics13:57
jki313:59
jki213:59
jki113:59
jki#topic Kernel testing13:59
*** brlogger changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:59
patersoncNot much news from me14:00
jkieverything's running smoothly then :)14:01
iwamatsuWe can not build 5.10.y/-cip tree yet.14:01
jki...except for...14:01
jkiwhat blocks it?14:02
alicefmNot much news from me either14:02
iwamatsugcc14:02
patersoncOh yes, I did an MR, we just need to update cip-pipeilnes to use it14:03
patersoncSorry14:03
iwamatsugcc of gitlab's kernel build container is not fit 5.10.y.14:03
iwamatsuNOP14:04
jkianything else here?14:06
*** patersonc[m] <patersonc[m]!~patersonc@2001:470:69fc:105::aaf> has joined #cip14:06
jki314:07
jki214:07
jki114:07
jki#topic AOB14:07
*** brlogger changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"14:07
jkiirc bot: we'll get a new one!14:07
alicefmok nice14:08
jkilikely. Neal dug out a hosting at LF, details to be clarified14:08
masamigreat!14:08
iwamatsunice14:08
jkialso if/how to get the archive migrated14:08
jkiany other business?14:09
jki314:10
jki214:10
jki114:10
jki#endmeeting14:10
brloggerMeeting ended Thu Feb  3 14:10:31 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:10
brloggerMinutes:        https://irclogs.baserock.org/meetings/cip/2022/02/cip.2022-02-03-13.08.html14:10
brloggerMinutes (text): https://irclogs.baserock.org/meetings/cip/2022/02/cip.2022-02-03-13.08.txt14:10
brloggerLog:            https://irclogs.baserock.org/meetings/cip/2022/02/cip.2022-02-03-13.08.log.html14:10
*** brlogger changes topic to "Civil Infrastructure Platform Project. Find the logs at https://irclogs.baserock.org/cip/"14:10
jkithanks all!14:10
iwamatsuthank you!14:10
ulithank you14:10
masamithank you14:10
*** josiah <josiah!~kvirc@pool-100-16-211-90.bltmmd.fios.verizon.net> has quit IRC14:11
jkibye, bye14:11
alicefthanks you14:11
*** patersonc <patersonc!~patersonc@host86-168-176-9.range86-168.btcentralplus.com> has quit IRC14:11
*** masami <masami!~masami@FL1-110-233-204-67.tky.mesh.ad.jp> has quit IRC14:12
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip14:13
*** uli <uli!~uli@55d466c9.access.ecotel.net> has left #cip14:13
*** jki <jki!~jki@165.225.27.1> has quit IRC14:20
*** lfam <lfam!~lfam@user/lfam> has joined #cip17:12
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has quit IRC17:38
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip18:26
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC19:07
*** monstr <monstr!~monstr@2a02:768:2307:40d6::f9e> has quit IRC19:12
*** lfam <lfam!~lfam@user/lfam> has quit IRC19:28
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has joined #cip19:47
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has quit IRC19:48
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has joined #cip19:48
*** toscalix <toscalix!~toscalix@251.red-83-52-125.dynamicip.rima-tde.net> has quit IRC19:49
*** rajm-and <rajm-and!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC22:49
« Wednesday, 2022-02-02 Index Friday, 2022-02-04 »

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