Yocto Technical Team Minutes, Engineering Sync, for June 1 2021

Yocto Technical Team Minutes, Engineering Sync, for June 1 2021

[Trevor Woerner]

Yocto Technical Team Minutes, Engineering Sync, for June 1 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Stephen Jolley, Colin McAllister, Armin Kuster, Joshua Watt,
Steve Sakoman, Saul Wold, Richard Purdie, Philip Ballister, Bruce Ashfield,
Randy MacLeod, Michael Ambrus, Michael Halstead, Daiane Angolini, Peter
Kjellerstedt, Trevor Gamblin, Ross Burton, Tim Orling, Alexandre Belloni,
Jan-Simon Möller, Scott Murray, Tony Tascioglu

== notes ==
- 3.4 M1 (honister) to be built next week
- 3.1.8 (dunfell) passed QA, waiting final approval for release
- CVE issue count: master=6, hardknott=14
- AUH to run more regularly
- multiconfig issues still not ironed out
- ptest based on core-image-minimal instead of core-image-sato
- record high levels of AB intermittent issues

== general ==
RP: AB int issues seemed to be helped by limited the number of threads used
    for compression


RP: two cases of trying to talk to upstream but found problems with our
    logging, upstream says “go away and fix your logging” before we can
    continue discussions


PeterK: question about yocto-poky tags
RP: we stopped adding “hardknott-pokyversion” (e.g. “hardknott-25.0”)
    tags and this broke PeterK’s workflow. i would prefer to move away from
    these tags and use yocto tags instead
PeterK: i’m okay moving to something new. “hardknott-3.3.1” would be
    better than “hardknott-25.0”. also, could we wait and not change this
    in the middle of a release series? (i.e. wait for the first release of
    honister).
RP: i need to talk to MichaelH and Vineela and figure something out
RP: this is part of a larger task to rationalize the release process a bit
    better (e.g. also need to tie in the documentation releases too with Nico)
RP: this tells us that people are using some of these things that we didn’t
    think were being used
MichaelH: Vineela and I have a couple other release things we need to go
    over, i’ll make a meeting. we could add tags going backwards so we
    can transition now. this would give us some correlation to the tags in
    openembedded etc


TimO: freenode?
RP: we didn’t do anything last week (due to Summit). i think Nico needs to
    coordinate with MichaelH. i believe we are moving over to libera.chat
Scott: fd.o seems to have moved to OFTC
TrevorW: do we have ops in #yocto and #oe?
RP: yes
TimO + PhilipB: we’ve got slack too
JPEW: matrix integration too?
TimO: yes Jan-Simon


JPEW: SBOM
RP: please discuss on licensing email list
RP: i think there’s a plugfest going on and i don’t think anyone from YP
    has signed up
Randy: Mark from WR is attending
RP: i’d like to fly the YP flag there
JPEW: details?
RP: https://docs.google.com/forms/d/e/1FAIpQLSdVOewc3uCZh39inX4X7QsA_jaQMqyrEiLFrWEZEpWxRCi3eQ/viewform
Philip: who’s interested in showing up at the plugfest?
JPEW: i would, but 22nd doesn’t work for me
Philip: i could go
??: what’s the layer?
Saul: meta-doubleopen
Ross: 22 doesn’t work for me either, but i could help put stuff together
    beforehand


TrevorW: videos for YPS are up
https://www.youtube.com/playlist?list=PLD4M5FoHz-TwWYbaJwduH8ZYNYvva76QQ
https://elinux.org/YPS_May2021_Presentations


Jan-Simon: what’s the procedure for updating layerindex?
RP: PaulE is an admin
Ross: I was added recently
RP: MichaelH who are the admins?
MichaelH: myself, PaulE, Ross, JaMa, Nico, Randy
TimO: PaulE recently added me too
J-S: there are a lot of issues with the layerindex (e.g. emails bouncing)


Randy: should we move the next monthly meeting to avoid the 4th of July?
RP: sounds good, we’ll move it to July 13th