Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 9: Line 9:


'''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 and 4.3 M3 is in QA
*YP 4.2.3 was released
*The numpy reproducibility issue is not solved unfortunately
*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 are continuing intermittent ptest issues for openssh and glib-networking amongst other issues
*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 testing for qemuppc and qemumips/qemumips64 has been reduced and we’re no longer testing core-image-sato-sdk on these platforms.
*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
*SPDX manifests are now enabled by default for OE-Core/nodistro as well as poky.
*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.
*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 24: Line 21:
**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
**Michael Opdenacker (Bootlin) will be working on the binary distro topic
The other remaining topic areas should be announced soon.
**Smile will be working on the meta-openembedded topic area
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.



Revision as of 14:41, 12 September 2023

Yocto Project Weekly Status September 12th, 2023

Current Dev Position: YP 4.3 M4 (Feature Freeze)
Next Deadline: 2nd October 2023 YP 4.3 M4 build date

Next Team Meetings:

Key Status/Updates:

  • We are now at feature freeze for 4.3 and 4.3 M3 is in QA
  • The numpy reproducibility issue is not solved unfortunately
  • There are continuing intermittent ptest issues for openssh and glib-networking amongst other issues
  • The testing for qemuppc and qemumips/qemumips64 has been reduced and we’re no longer testing core-image-sato-sdk on these platforms.
  • SPDX manifests are now enabled by default for OE-Core/nodistro as well as poky.
  • 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’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
    • Smile will be working on the meta-openembedded topic area

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 is in QA
  • YP 4.3 M4 build date 2023/10/02
  • YP 4.3 M4 Release date 2023/10/27

Upcoming dot releases:

  • 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