Current Dev Position: YP 5.1 M1

Next Deadline: YP 5.1 M1 Build 20 May 2024

Next Team Meetings:

• Bug Triage meeting Thursday May 16th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)

• Weekly Project Engineering Sync Tuesday May 14th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)

• Twitch -  See https://www.twitch.tv/theyoctojester 

Key Status/Updates:

• YP 4.0.18 has been released

• YP 5.0.1 rc2 is in QA.

• YP 5.0.1 rc1 was abandoned due to high numbers of intermittent failures.

• There are some CVE related announcements which are helpful to us:

• There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective

• CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment

• There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990

Please consider signing this to show support for those changes.

Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.

• The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date. 

• The WORKDIR to UNPACKDIR transition and redefinition of UNPACKDIR now has patches under testing in master-next, including updates to recipetool and devtool which pass our automated tests.

• gcc 14 has patches pending thanks for Khem and Martin in particular. Merging the new gcc version is needed to generate new uninative tarballs to support Fedora 40 builds or any other distro using the new gcc version.

• The project is in the process of testing a new way of hosting our autobuilder with plans to switch soon if successful. Our existing hardware is past end of life and showing increased hardware failures so is currently down on capacity meaning builds are taking longer than normal.

• Mailing list changes now mean any google hosted email accounts have the mailing list From: address rewritten. This had impacted our ability to handle patches but key maintainers now have workarounds for this.

• Our automated tests have been seeing a number of intermittent issues. An email was sent detailing a few of these and the response with several patches or patches in progress has been extremely helpful and they’re very gratefully received.

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: 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 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_Unassigned_Enhancements/Bugs

• 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 

• We have a growing number of bugs in bugzilla, any help with them is appreciated.

• Regarding bugs, even if you can’t fix a bug, submitting a failing test case that can reproduce the issue significantly improves the chances it might get fixed.

Tracking Metrics:

• WDD 2740 (last week 2720) (https://wiki.yoctoproject.org/charts/combo.html)

• OE-Core/Poky Patch Metrics

• Total patches found: 1128 (last week 1125)

• Patches in the Pending State: 221 (20%) [last week 221 (20%)]

• https://autobuilder.yocto.io/pub/non-release/patchmetrics/

YP 5.1 Milestone Dates:

• YP 5.1 M1 Build date  2024-05-20

• YP 5.1 M1 Release date 2024-05-31

• YP 5.1 M2 Build date  2024-07-08

• YP 5.1 M2 Release date 2024-07-19

• YP 5.1 M3 Build date  2024-08-26

• YP 5.1 M3 Release date 2024-09-06

• YP 5.1 M4 Build date  2024-09-30

• YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

• YP 4.0.18 is released.

• YP 5.0.1 is in QA.

• YP 4.0.19 build date 2024-06-03

• YP 4.0.19 Release date 2024-06-14

• YP 5.0.2 Build Date 2024-06-24

• YP 5.0.2 Release Date 2024-07-05

• YP 4.0.20 Build Date 2024-07-15

• YP 4.0.20 Release Date 2024-07-26

• YP 5.0.3 Build Date 2024-08-12

• YP 5.0.3 Release Date 2024-08-23

• YP 4.0.21 Build Date 2024-09-09

• YP 4.0.21 Release Date 2024-09-20

• YP 5.0.4 Build Date 2024-09-23

• YP 5.0.4 Release Date 2024-10-04

• YP 4.0.22 Build Date 2024-10-14

• YP 4.0.22 Release Date 2024-10-25

• YP 5.0.5 Build Date 2024-11-11

• YP 5.0.5 Release Date 2024-11-22

• YP 4.0.23 Build Date 2024-11-18

• YP 4.0.23 Release Date 2024-11-29

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!]