Yocto Project Status 16 April 2024 (WW16)
Stephen K Jolley <[email protected]> Tue, 16 Apr 2024 07:44:04 -0700
| Newsgroups | org.yoctoproject.lists.yocto-status |
|---|---|
| Message-ID | <20240416144404.yN0pTPedwskj83qKv6ud1SdUTCDIGTVxoxy1CLKFXE4@z> |
Current Dev Position: YP 5.0 preparing to build rc2
Next Deadline: 1st April 2024 YP 5.0 M4 build
Next Team Meetings:
-
Bug Triage meeting Thursday April 18th at 7:30 am PST (
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
-
Weekly Project Engineering Sync Tuesday April 16th at 8 am PST (
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
<https://zoom.us/j/990892712>
-
Twitch - See https://www.twitch.tv/theyoctojester
Key Status/Updates:
-
YP 5.0 rc1 is building but has many (6+) failures in the build so will
have to be abandoned.
-
The final dunfell build will follow 5.0 into QA.
-
The master branch has diverged from scarthgap.
-
For 5.0, we were able to switch to the new hash equivalence server
however the need for websockets complicated the worker configuration and
needed new buildtools tarball versions which are causing various problems.
-
During the rc1 build as well as pip and setuptools issues within
buildtools, we also saw a qemuppc boot issue, an instance of the spdx
dependency problem, an sstate mirror issue and a github network error. This
highlights how important fixing these is over the release cycle. The volume
of these may impact our ability to maintain the LTS.
-
Thanks to everyone who sent documentation patches, we’re in much better
shape with the migration guide and release notes now. Further improvements
are still very welcome.
-
The “Binary Distro” work is now well underway and there are PR Server
passthrough and image testing patches under review. The wiki page
<https://wiki.yoctoproject.org/wiki/Binary_Distro_Prototype#Policies_and_Processes>
has had a number of policy/process proposals documented, help is welcome to
help improve these, or highlight where further documentation is needed.
-
There are patches for improving the build performance graphs in review.
Sample output from the changes is here
<http://autobuilder.yocto.io/pub/non-release/20240413-21/testresults/buildperf-alma8/perf-alma8_master-next_20240413135138_904bb385c3.html>
and here
<http://autobuilder.yocto.io/pub/non-release/20240413-19/testresults/buildperf-debian11/perf-debian11_master-next_20240413064005_7116cd908d.html>
.
-
There are also patches under review for the patch/cve metrics page to
improve the usability.
-
We continue to watch the NIST NVD (CVE database) situation, the recent
update didn’t clarify much. Unfortunately there doesn’t appear to be a
clear path forward as yet but using data directly from MITRE may help give
partial information. These issues are making it hard to know what to
include in the 5.0 release as it isn’t clear which changes are security
related.
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.0. See:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_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
<https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
-
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.
YP 5.0 Milestone Dates:
-
YP 5.0 is building
-
YP 5.0 M4 Release date 2024/04/30
YP 5.1 Proposed 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.3.4 is released.
-
YP 3.1.33 build date 2024-04-15
-
YP 3.1.33 Release date 2024-04-26
-
YP 4.0.18 build date 2024-04-22
-
YP 4.0.18 Release date 2024-05-03
-
YP 4.0.19 build date 2024-06-03
-
YP 4.0.19 Release date 2024-06-14
Upcoming Proposed dot releases:
-
YP 5.0.1 Build Date 2024-05-13
-
YP 5.0.1 Release Date 2024-05-24
-
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
Tracking Metrics:
-
WDD 2719 (last week 2696) (
https://wiki.yoctoproject.org/charts/combo.html)
-
OE-Core/Poky Patch Metrics
-
Total patches found: 1173 (last week 1174)
-
Patches in the Pending State: 249 (21%) [last week 249 (21%)]
-
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*: *s
<[email protected]>[email protected] <[email protected]>*