Yocto Technical Team Minutes, Engineering Sync, for August 11 2020

Trevor Woerner

Yocto Technical Team Minutes, Engineering Sync, for August 11 2020
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, Armin Kuster, Bruce Ashfield, Jan-Simon
Möller, Tim Orling, Jeremey Puhlmann, Paul Barker, Mark Morton, Alejandro
H, Randy MacLeod, Michael Halstead, Richard Purdie, Trevor Gamblin,
(callin), Ross Burton, Peter Kjellerstedt, Steve Sakoman

== notes ==
- 3.2-M2 out of QA, in final release process, looks good
- now in 3.2-M3, last milestone for features
- 3.2-M4, in september, only for bug fixes
- 3.0.4 (last Zeus) should be built and out this week (if all goes well),
this is the “stutter step”, then we go to 6 months
- some more AB failures added to the list
- some 3.2 bugs that don’t have owners

== general ==
RP: some “old” AB failures have reappeared, perhaps a lock file issue in
RP: there is a package data one that might be debuggable and reproducible

RP: relatively quiet week, a couple bitbake patches (<something?>, colourizing

MarkM: what’s the next step for sphinx?
RP: a list was made of the areas to work on (from Nico), we just need people
to sign up
RP: the one I’m going to look at is how to get the versioning to work on the

PaulB: meta-kernel layer, seems to be some issues with naming
Ross: we have been using meta-kernel, i can see an argument to rename to
meta-mainline-kernel, perhaps, since meta-kernel is a bit generic
RP: my concern is that meta-kernel doesn’t convey what it does
PaulB: my intention was to make it a common place for common kernels (e.g.
Linaro kernel can be used on a bunch of ARM boards). also my hope was to
support back to kernels that aren’t “current” (e.g. 4.4). so it’s
not just a “mainline” layer
RP: i believe there’s a way to get the mainline kernel with linux-yocto
PaulB: i need to be able to flick customers between, e.g. a 4.4 and a mainline
TrevorW: the magic to get mainline with linux-yocto is to set
PREFERRED_PROVIDER to linux-yocto-dev
RP: it’s a tricky situation, Bruce does a lot of work, sometimes work that
doesn’t show up on the mailing list, I think collaborating with him
would be a good approach. linux-yocto was created to reduce fragmentation.
sometimes understanding linux-yocto can be tricky.
PaulB: maybe just carrying any differences that we need relative to
linux-yocto might be better. some of my customers just want a raw mainline
(with no other patches) since they also support e.g. Debian
Timo: one of the things i do over and over is explaining linux-yocto to people
and how to use it
TrevorW: it was my intent to explain scc files and kernel patches with the
last talk i gave at devday, if there are suggestions please let me know.
hopefully those videos get published
Armin: one can use kernel branch overrides to use the v5.4/base (of
RP: maybe we need more docs or information
PaulB: meta-kernel was meant to be lightweight, it doesn’t get as much
testing as linux-yocto, it wasn’t meant to step on anyone’s toes
Timo: maybe this is an opportunity to take a look at the kernel development
manual and make sure it is up to date
RP: maybe we could put a barebones kernel mainline recipe for the versions
that are in each release (i’m not saying that’s a good idea, i’m
just throwing out ideas), or maybe add more testing on AB for the
variations of kernels that area already in each release (e.g. the -rt
PaulB: this all sounds good
TrevorW: a suggestion: rename recipes-kernel/linux to
recipes-kernel/linux-yocto and then create a recipes-kernel/linux-mainline
for PaulB’s work?
RP: that would only make sense under the assumption that this would be merged
in oe-core
PaulB: we’re a ways off from that conversation, if ever
PaulB: i don’t think this is something that’s going to get resolved for
M3, but maybe sometime after

Join yocto@lists.yoctoproject.org to automatically receive all group messages.