Current Dev Position: YP 4.2 M4

Next Deadline: 3rd April 2023 YP 4.2 M4 Build

Next Team Meetings:

• Bug Triage meeting Thursday March 16th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
• Weekly Project Engineering Sync Tuesday March 14th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
• Twitch -  See https://www.twitch.tv/theyoctojester

Key Status/Updates:

• YP 4.0.8 was released
• YP 4.1.3 passed QA and is due to be released
• We are now in feature freeze for 4.2 and preparing for final build in ~2.5 weeks
• Patches continue to merge into master and there are some good bug fixes in there. Some version upgrades are merging either due to low risk or due to the likely need from other components during the lifetime of the release.
• Support for parallel ptest execution with a ptest per image was merged, along with various dependency fixes for the ptest packages to ensure this works as expected. This takes ptest execution time from 3.5 hours to around 45 minutes on the autobuilder.
• The bugzilla was upgraded to the version 5 series which brings access to the REST API and functionality useful to the triage team. Testopia was dropped.
• Regression reports for release builds are now looking fairly accurate
• CVE levels in the LTS releases are at higher levels than they have been for a while which is a concern.
• 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
• There are bugs that are currently unassigned for YP 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.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/maintainers.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.
• Help us resolve CVE issues: CVE metrics 

YP 4.2 Milestone Dates:

• YP 4.2 M4 build date 2023/04/03
• YP 4.2 M4 Release date 2023/04/28

Upcoming dot releases:

• YP 4.0.8 is released
• YP 4.1.3 is ready for release
• 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 2472 (last week 2497) (https://wiki.yoctoproject.org/charts/combo.html)
• OE-Core/Poky Patch Metrics
• Total patches found: 1185 (last week 1185)
• Patches in the Pending State: 277 (23%) [last week 277 (23%)]
• 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

The Status reports are now stored on the wiki at: 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:              sjolley.yp.pm@...