Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status August 29th, 2023 ==
== Yocto Project Weekly Status September 5th, 2023 ==
Current Dev Position: YP 4.3 Feature Freeze<br/>
Current Dev Position: YP 4.3 Feature Freeze<br/>
Next Deadline: 28th August 2023 YP 4.3 M3 build date<br/>
Next Deadline: 28th August 2023 YP 4.3 M3 build date<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday August 31st 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday September 7th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday August 29th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday September 5th 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.
*We are now at feature freeze for 4.3.
*YP 4.0.12 was released
*YP 4.2.3 was released
*YP 4.2.3 is due to be released
*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.
*The qemuppc ssh command hangs continues to be a mystery. It seems to be something in recent master that regressed it but it isn’t the kernel, the binutils upgrade, systemd or glibc or qemu. We’ve not seen any other hangs so the x86 issues may have been something else.
*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.
*The acl/xattr changes are blocked on a hard requirement on tar 1.35, it is unclear how we’d achieve that in all cases.
*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
*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.
*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.
*We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
*We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
*The M3 build will depend upon reaching conclusions in several of these areas
*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.
*M3 will build when we have a resolution to the qemu 8.1.0 issue and ideally fixes for the intermittent ptest issues.
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
**Marta Rybczynska will be working on the security topic
**Marta Rybczynska will be working on the security topic
Line 22: Line 23:
**Savoir-faire Linux will be working on the toaster and VSCode topics
**Savoir-faire Linux will be working on the toaster and VSCode topics
**BayLibre will be working on the patchtest and project tooling topics
**BayLibre will be working on the patchtest and project tooling topics
**Michael Opdenacker (Bootlin) will be working on the binary distro topic
The other remaining topic areas should be announced soon.
The other remaining topic areas should be announced soon.
We’d also note that Tim Orling (Konsulko) will be working on the layer index.
We’d also note that Tim Orling (Konsulko) will be working on the layer index.
Line 41: Line 43:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.12 is released
*YP 4.2.3 is released
*YP 4.2.3 is ready for release
*YP 3.1.28 build date 2023/09/18
*YP 3.1.28 build date 2023/09/18
*YP 3.1.28 Release date 2023/09/29
*YP 3.1.28 Release date 2023/09/29
Line 59: Line 60:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2500 (last week 2488) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2500 (last week 2500) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1188 (last week 1183)
**Total patches found: 1185 (last week 1188)
**Patches in the Pending State: 258 (22%) [last week 258 (22%)]
**Patches in the Pending State: 254 (21%) [last week 258 (22%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/



Revision as of 14:44, 5 September 2023

Yocto Project Weekly Status September 5th, 2023

Current Dev Position: YP 4.3 Feature Freeze
Next Deadline: 28th August 2023 YP 4.3 M3 build date

Next Team Meetings:

Key Status/Updates:

  • We are now at feature freeze for 4.3.
  • YP 4.2.3 was released
  • 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.
  • 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.
  • 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
  • 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.
  • We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
  • 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.
  • M3 will build when we have a resolution to the qemu 8.1.0 issue and ideally fixes for the intermittent ptest issues.
  • We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
    • Marta Rybczynska will be working on the security topic
    • Alexander Kanvin will be working on the core workflow topic
    • Savoir-faire Linux will be working on the toaster and VSCode topics
    • BayLibre will be working on the patchtest and project tooling topics
    • Michael Opdenacker (Bootlin) will be working on the binary distro topic

The other remaining topic areas should be announced soon. We’d also note that Tim Orling (Konsulko) will be working on the layer index.

Ways to contribute:

YP 4.3 Milestone Dates:

  • 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:

  • 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:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives