Skip to contentSkip to conversation

Yocto Project Status 10 January 2023 (WW02)

DISCUSSION [email protected] 1 participant 1 message Jan 10, 2023

lore
Share & tools
lore
#0 lore raw

Current Dev Position: YP 4.2 M2

Next Deadline: 23rd January 2023 YP 4.2 M2 Build

Next Team Meetings:

* Bug Triage meeting Thursday January 12th 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Weekly Project Engineering Sync Tuesday January 10th at 8 am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
* Twitch - See <https://www.twitch.tv/theyoctojester>
https://www.twitch.tv/theyoctojester

Key Status/Updates:

* YP 4.1.2 is in QA
* A large number of package upgrades have merged bringing us up to
date with various upstreams.
* We have started moving code out of core bbclass files into the
function libraries to help reduce parsing memory use, volumes of data transfer and sstate signature data sizes. Help is welcome in developing further patches to improve our function libraries.
* The autobuilder controller has been relocated to deal with
connectivity issues, we do have some issues to iron out before things are back to normal service. We were unable to upgrade the buildbot version as there were too many other moving pieces.
* We are trying to upgrade uninative to include libgcc to deal with
pthread_cancel failures. Newer versions of patchelf are proving problematic and appear to be causing segfaults and we're trying to untangle this from other issues.
* We have reverted the tune for qemux86-64 back to corei7-64 since we
still have v2 hardware that won't work properly with v3 under KVM and similar.
* A uninative bug has been exposed by recent bitbake datastore
improvements which could cause sstate to be missed/duplicated.
* We merged a number of neat rust improvements which add on target
cargo support and added automated QA tests for this functionality so we can ensure it continues to work and doesn't regress. Thanks Alex Kiernan, we hope to see more series like this one!
* CVE levels in master are becoming worrying again, help would be
appreciated to address the open issues.
* The autobuilder maintenance window now occurs on Mondays.
* We have a growing number of bugs in bugzilla, any help with them is
appreciated.

Ways to contribute:

* As people are likely aware, the project has a number of components
which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: patchtest, layerindex, devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
* There are bugs identified as possible for newcomers to the project:
<https://wiki.yoctoproject.org/wiki/Newcomers>
https://wiki.yoctoproject.org/wiki/Newcomers
* There are bugs that are currently unassigned for YP 4.2. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhan
cements.2FBugs
* We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:
<http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/mai
ntainers.inc>
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to "Unassigned" soon to help facilitate this.
* Help is very much welcome in trying to resolve our autobuilder
intermittent issues. You can see the list of failures we're continuing to see by searching for the "AB-INT" tag in bugzilla:
<https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT>
https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
* Help us resolve CVE issues:
<https://autobuilder.yocto.io/pub/non-release/patchmetrics/> CVE metrics

YP 4.2 Milestone Dates:

* YP 4.2 M2 build date 2023/01/23
* YP 4.2 M2 Release date 2023/02/03
* YP 4.2 M3 build date 2023/02/20
* YP 4.2 M3 Release date 2023/03/03
* YP 4.2 M4 build date 2023/04/03
* YP 4.2 M4 Release date 2023/04/28

Upcoming dot releases:

* YP 4.1.2 built and in QA
* YP 4.1.2 Release date 2023/01/20
* YP 3.1.22 build date 2023/01/16
* YP 3.1.22 Release date 2023/01/27
* YP 4.0.7 build date 2023/01/30
* YP 4.0.7 Release date 2023/02/10
* YP 3.1.23 build date 2023/02/13
* YP 3.1.23 Release date 2023/02/24
* YP 4.0.8 build date 2023/02/27
* YP 4.0.8 Release date 2023/03/10
* YP 4.1.3 build date 2023/03/06
* YP 4.1.3 Release date 2023/03/17
* YP 3.1.24 build date 2023/03/20
* YP 3.1.24 Release date 2023/03/31
* YP 4.0.9 build date 2023/04/10
* YP 4.0.9 Release date 2023/04/21
* YP 4.1.4 build date 2023/05/01
* YP 4.1.4 Release date 2023/05/13
* YP 3.1.25 build date 2023/05/08
* YP 3.1.25 Release date 2023/05/19
* YP 4.0.10 build date 2023/05/15
* YP 4.0.10 Release date 2023/05/26

Tracking Metrics:

* WDD 2447 (last week 2457) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics

* Total patches found: 1176 (last week 1189)
* Patches in the Pending State: 281 (24%) [last week 282 (24%)]

* <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
https://autobuilder.yocto.io/pub/non-release/patchmetrics/

The Yocto Project's technical governance is through its Technical Steering Committee, more information is available at:

<https://wiki.yoctoproject.org/wiki/TSC>
https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at:
<https://wiki.yoctoproject.org/wiki/Weekly_Status>
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you'd like to see on this weekly status update, let us know!]

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

* Cell: (208) 244-4460

* Email: [email protected]
<mailto:[email protected]>