Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 11: Line 11:
'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now at feature freeze for YP 3.4
*We are now at feature freeze for YP 3.4
*Read-only PRServ and switch to asyncio was merged
*Rust was merged into core, it was touch and go whether we could/would or not. Unfortunately there was an error found after merging with cargo-native on centos7 hosts which we still need to resolve before building M3.
*Rust merging to core is proving problematic due to issues interacting with uninative. These cause many strange autobuilder failures so this issue would have to be addressed in the next day or two in order to be in 3.4.
*Fixes for glibc 2.34 and pseudo were merged however this uses a binary shim and isn’t an ideal way to solve the issues. We need to find a way to have active development on pseudo with investigation into possible replacement approaches.
*glibc 2.34 and the merge of the various libraries into libc is causing significant problems for pseudo. This issue is causing significant worry as the project will struggle as distros adopt the new glibc version unless we work out how to fix things.
*A kernel issue introduced in recent kernel module versioning changes needs to resolved before we can build M3.
*The tune file layout change was merged.
*The glibc 2.34 upgrade caused issues with docker and the clone3 syscall returning EPERM instead of ENOSYS. We will likely have to add a workaround to our glibc until released versions of docker have the upstream fix.
*We are still hoping to get some of the planned SBOM work into 3.4
*Intermittent issues are ongoing and help is very much welcome on these 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
*Intermittent issues are ongoing and help is very much welcome on these 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


Revision as of 14:36, 31 August 2021

Yocto Project Weekly Status Aug. 31, 2021

Current Dev Position: YP 3.4 M3 (Feature Freeze)
Next Deadline: 23rd Aug. 2021 YP 3.4 M3 build (Feature Freeze)

Next Team Meetings:

Key Status/Updates:

  • We are now at feature freeze for YP 3.4
  • Rust was merged into core, it was touch and go whether we could/would or not. Unfortunately there was an error found after merging with cargo-native on centos7 hosts which we still need to resolve before building M3.
  • Fixes for glibc 2.34 and pseudo were merged however this uses a binary shim and isn’t an ideal way to solve the issues. We need to find a way to have active development on pseudo with investigation into possible replacement approaches.
  • A kernel issue introduced in recent kernel module versioning changes needs to resolved before we can build M3.
  • The glibc 2.34 upgrade caused issues with docker and the clone3 syscall returning EPERM instead of ENOSYS. We will likely have to add a workaround to our glibc until released versions of docker have the upstream fix.
  • Intermittent issues are ongoing and help is very much welcome on these 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

Ways to contribute:

YP 3.4 Milestone Dates:

  • YP 3.4 M3 build date 2021/08/23
  • YP 3.4 M3 Release date 2021/09/03
  • YP 3.4 M4 build date 2021/10/04
  • YP 3.4 M4 Release date 2021/10/29

Planned upcoming dot releases:

  • YP 3.1.11 build date 2021/09/13
  • YP 3.1.11 release date 2021/9/24

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

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