Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(28 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status March 12th, 2024 ==
== Yocto Project Weekly Status July 23rd, 2024 ==
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Current Dev Position: YP 5.1 M3 <br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>
Next Deadline: YP 5.1 M3 Build 26 Aug. 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday March 14th 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 March 12th 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 M3 is in QA
*YP 4.0.20 is due to be released
*YP 3.1.32 was released
*YP 5.1 M2 is in QA
*A key worry now is the documentation for the release, especially given it is an LTS
*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
*The QA screenshot changes were merged but not enabled as there were too many bugs still present.
*SPDX 3.0 has merged and is now the default.
*The go upgrade to 1.22 did merge
*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.
*We are seeing issues with devtool tests changing metadata and causing race issues. It is unclear why we’re seeing these now.
*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.
*The opkg lock issue with systemd images continues to be a significant concern for the release.
*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 previously reported CVE database update issue on the autobuilder has not been addressed yet. This is causing higher numbers of CVEs to be reported on the autobuilder generated charts.
*Further help on optimizing build disk usage would be most welcome.
*There have been questions about official RISC-V support in this next release, especially since it is an LTS. We will trial qemuriscv64 support in M3 but remove it before the final LTS release as there is no sponsor for that support.
*Some larger patches still need help with review these would be appreciated:
**Improved CVE tooling from Marta
**kernel fitimage changes from Adrian
**bitbake-setup and configuration fragments from Alexander
*We’ve been trying to resolve some of the longer standing patches in review and are getting more caught up.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*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!
*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 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
*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.
*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 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  
*Help us resolve CVE issues: CVE metrics  
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M3 is in QA.
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30
'''Upcoming dot releases:'''<br/>
*YP 3.1.32 was released.
*YP 4.0.17 build date 2024/03/11
*YP 4.0.17 Release date 2024/03/22
*YP 4.3.4 build date 2024/03/25
*YP 4.3.4 Release date 2024/04/05
*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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2688 (last week 2618) (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: 1148 (last week 1155)
**Total patches found: 1079 (last week 1082)
**Patches in the Pending State: 249 (22%) [last week 249 (22%)]
**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 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:'''<br/>
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

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