Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(56 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status September 5th, 2023 ==
== Yocto Project Weekly Status May 21st, 2024 ==
Current Dev Position: YP 4.3 Feature Freeze<br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: 28th August 2023 YP 4.3 M3 build date<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday September 7th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday May 23rd at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday September 5th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday May 21st 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/>
*We are now at feature freeze for 4.3.
*YP 5.0.1 has been through QA and is pending review for release
*YP 4.2.3 was released
*There are some CVE related announcements which are helpful to us:
*The qemupcc issue was tracked down to the glibc 2.38 included in the new uninative version. Upgrading along the glibc stable branch appeared to resolve the issue. It seems ppc was worst affected as the emulation is slow.
**There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
*We’re hoping to have tracked down the numpy reproducibility issue to non-deterministic blas library queries but we didn’t definitively work out which system was introducing the issue so we can’t be sure it is resolved.
**CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
*We need to upgrade to qemu 8.1.0 for security fixes but it is broken for x86. If we backport fixes for that issue, mips virtio breaks. We’ve filed a bug upstream: https://gitlab.com/qemu-project/qemu/-/issues/1866
*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
*Patches have been resubmitted to radically alter the do_unpack process for license compliance reasons. The code is complex and hard to understand and will have a performance impact on builds as well as making things hard to debug. *The risk of not taking the changes is that for some legal departments, the SPDX data isn’t detailed enough. The compromise between performance and ease of use vs. legal requirements is a tough one. We don’t really want to have two codepaths either. Feedback/review on the series welcome.
**Please consider signing this to show support for those changes.
*We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
**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.
*Due to the number of issues related to mips and ppc being encountered with few people interested in helping fix them, we are likely to reduce the amount of testing being done on those targets before release. If you’re using these targets please let us know as we’re likely to drop them if there are no users.
*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!)
*M3 will build when we have a resolution to the qemu 8.1.0 issue and ideally fixes for the intermittent ptest issues.
*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.
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
*More of the WORKDIR to UNPACKDIR transition has merged and devtool oe-local-files support has been dropped.
**Marta Rybczynska will be working on the security topic
*The next stage of the WORKDIR changes is pending testing in master-next.
**Alexander Kanvin will be working on the core workflow topic
*The aim is to build YP 5.1 M1 as soon as the various queued patches stabilize.
**Savoir-faire Linux will be working on the toaster and VSCode topics
*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.
**BayLibre will be working on the patchtest and project tooling topics
*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.
**Michael Opdenacker (Bootlin) will be working on the binary distro topic
*Two issues causing failures on the new test infrastructure were tracked down to problems in bitbake. Both were effectively timing related issues.
The other remaining topic areas should be announced soon.
PR server pass through support merged.
We’d also note that Tim Orling (Konsulko) will be working on the layer index.
*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/>
*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 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*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 4.3 Milestone Dates:'''<br/>
*YP 4.3 M3 build date  2023/08/28
*YP 4.3 M3 Release date 2023/09/08
*YP 4.3 M4 build date  2023/10/02
*YP 4.3 M4 Release date 2023/10/27
'''Upcoming dot releases:'''<br/>
*YP 4.2.3 is released
*YP 3.1.28 build date 2023/09/18
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.13 build date 2023/09/25
*YP 4.0.13 Release date 2023/10/06
*YP 3.1.29 build date 2023/10/30
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.14 build date 2023/11/06
*YP 4.0.14 Release date 2023/11/17
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2500 (last week 2500) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2752 (last week 2740) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1185 (last week 1188)
**Total patches found: 1127 (last week 1128)
**Patches in the Pending State: 254 (21%) [last week 258 (22%)]
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
*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 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:'''<br/>
*YP 5.0.1 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 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/>
Line 70: Line 80:


== Archives ==
== Archives ==
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]

Revision as of 14:44, 21 May 2024

Yocto Project Weekly Status May 21st, 2024

Current Dev Position: YP 5.1 M1
Next Deadline: YP 5.1 M1 Build 20 May 2024

Next Team Meetings:

Key Status/Updates:

  • YP 5.0.1 has been through QA and is pending review for release
  • 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. Marta sent out an update last week on this (thanks!)
  • 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.
  • More of the WORKDIR to UNPACKDIR transition has merged and devtool oe-local-files support has been dropped.
  • The next stage of the WORKDIR changes is pending testing in master-next.
  • The aim is to build YP 5.1 M1 as soon as the various queued patches stabilize.
  • 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.
  • 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:

Tracking Metrics:

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 5.0.1 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 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