Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status May 21st, 2024 ==
== Yocto Project Weekly Status July 23rd, 2024 ==
Current Dev Position: YP 5.1 M1 <br/>
Current Dev Position: YP 5.1 M3 <br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>
Next Deadline: YP 5.1 M3 Build 26 Aug. 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday May 23rd at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday July 25th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday May 21st at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday July 23rd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.0.1 has been through QA and is pending review for release
*YP 4.0.20 is due to be released
*There are some CVE related announcements which are helpful to us:
*YP 5.1 M2 is in QA
**There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
*There is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
**CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
*SPDX 3.0 has merged and is now the default.
*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
*We updated to glibc 2.40, thanks Khem. There is an issue with building pseudo under the new glibc version which is being worked on.
**Please consider signing this to show support for those changes.
*We identified an issue which meant warnings/errors in nativesdk recipes were not showing on our autobuilder. We have the fix for the CI issue ready as soon as we fix those warnings/errors, the gcc path problems are proving tricky.
**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.
*We were able to optimize some space usage in builds, thanks Ross. The results are visible on our performance charts, e.g.: https://autobuilder.yocto.io/pub/non-release/20240723-5/testresults/buildperf-alma8/perf-alma8_master_20240723030045_28fd497a26.html https://autobuilder.yocto.io/pub/non-release/20240723-4/testresults/buildperf-debian11/perf-debian11_master_20240722200022_28fd497a26.html
*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. Marta sent out an update last week on this (thanks!)
*Further help on optimizing build disk usage would be most welcome.
*gcc 14 has merged to master. There are errors in meta-arm, meta-virtualization and meta-mingw. Now that has merged, we will build and release a new uninative version.
*Some larger patches still need help with review these would be appreciated:
*More of the WORKDIR to UNPACKDIR transition has merged and devtool oe-local-files support has been dropped.
**Improved CVE tooling from Marta
*The next stage of the WORKDIR changes is pending testing in master-next.
**kernel fitimage changes from Adrian
*The aim is to build YP 5.1 M1 as soon as the various queued patches stabilize.
**bitbake-setup and configuration fragments from Alexander
*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.
*We’ve been trying to resolve some of the longer standing patches in review and are getting more caught up.
*Automated testing continues to show large numbers of problems (e.g. a reproducibility issue in spirv-tools) but we continue to work through and fix issues as quickly as we can.
*Two issues causing failures on the new test infrastructure were tracked down to problems in bitbake. Both were effectively timing related issues.
PR server pass through support merged.
*A rust build issue of x86 hosted builds vs arm hosted builds has been identified as the cause of intermittent failures. Whilst this can be fixed, the fix breaks tests and/or reproducibility which gives challenges given the need to fix scarthgap. There are also challenges upgrading to newer rust versions.
*The performance graph improvements have merged.
*Improvements to the patch and CVE metrics page have also merged.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 39: Line 33:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2752 (last week 2740) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2782 (last week 2787) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1127 (last week 1128)
**Total patches found: 1079 (last week 1082)
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
**Patches in the Pending State: 178 (16%) [last week 178 (17%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 M1 Build date 2024-05-20
*YP 5.1 M2 is in QA.
*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 Build date 2024-08-26
*YP 5.1 M3 Release date 2024-09-06
*YP 5.1 M3 Release date 2024-09-06
Line 56: Line 47:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.1 is ready for release.
*YP 4.0.20 is ready for release.
*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 Build Date 2024-08-12
*YP 5.0.3 Release Date 2024-08-23
*YP 5.0.3 Release Date 2024-08-23

Revision as of 14:48, 23 July 2024

Yocto Project Weekly Status July 23rd, 2024

Current Dev Position: YP 5.1 M3
Next Deadline: YP 5.1 M3 Build 26 Aug. 2024

Next Team Meetings:

Key Status/Updates:

Ways to contribute:

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M2 is in QA.
  • 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.20 is ready for release.
  • 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

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86401"