Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(159 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status September 12th, 2023 ==
== Yocto Project Weekly Status Jan. 6th, 202 ==
Current Dev Position: YP 4.3 M4 (Feature Freeze)<br/>
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: 2nd October 2023 YP 4.3 M4 build date<br/>
Next Deadline: YP 6.0 M1 Build Date 2026-01-05<br/>
6
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday September 14th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday September 12th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*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.15 is in QA
*YP 4.2.3 was released
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*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 have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*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.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*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
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*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.
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*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 exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*M3 will build when we have a resolution to the qemu 8.1.0 issue and ideally fixes for the intermittent ptest issues.
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..
*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:'''<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 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
*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 identified as possible for newcomers to the project: https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*Ongoing project development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing We need to continue to develop this as it will allow us to potentially find ways to fund specific work items.
'''Tracking Metrics:'''<br/>
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
'''YP 6.0 Milestone Dates:'''<br/>
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26


'''YP 4.3 Milestone Dates:'''<br/>
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.28 build date 2023/09/18
*YP 5.0.15 in QA.
*YP 3.1.28 Release date 2023/09/29
*YP 5.3.1 Build Date 2026-01-12
*YP 4.0.13 build date 2023/09/25
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.13 Release date 2023/10/06
*YP 4.0.33 Build Date 2026-01-26
*YP 3.1.29 build date 2023/10/30
*YP 4.0.33 Release Date 2026-01-30
*YP 3.1.29 Release date 2023/11/10
*YP 5.0.16 Build Date 2026-02-09
*YP 4.0.14 build date 2023/11/06
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.14 Release date 2023/11/17
*YP 5.3.2 Build Date 2026-02-16
*YP 4.2.4 build date 2023/11/13
*YP 5.3.2 Release Date 2026-02-27
*YP 4.2.4 Release date 2023/11/24
*YP 4.0.34 Build Date 2026-02-23
*YP 3.1.30 build date 2023/12/11
*YP 4.0.34 Release Date 2026-03-06
*YP 3.1.30 Release date 2023/12/22
*YP 5.3.3 Build Date 2026-03-09
*YP 4.0.15 build date 2023/12/18
*YP 5.3.3 Release Date 2026-03-20
*YP 4.0.15 Release date 2023/12/29
*YP 5.0.17 Build Date 2026-03-16
 
*YP 5.0.17 Release Date 2026-03-23
'''Tracking Metrics:'''<br/>
*YP 4.0.35 Build Date 2026-04-06
*WDD 2530 (last week 2500) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0.35 Release Date 2026-04-17
*OE-Core/Poky Patch Metrics
*YP 5.3.4 Build Date 2026-04-13
**Total patches found: 1186 (last week 1185)
*YP 5.3.4 Release Date 2026-04-24
**Patches in the Pending State: 255 (22%) [last week 254 (21%)]
*YP 5.0.18 Build Date 2026-04-20
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05


'''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 68: Line 79:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[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]]

Latest revision as of 15:43, 6 January 2026

Yocto Project Weekly Status Jan. 6th, 202

Current Dev Position: YP 6.0 M1
Next Deadline: YP 6.0 M1 Build Date 2026-01-05
6 Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 5.0.15 is in QA
  • YP 6.0 M1 will build when the 5 open high bugs are resolved.
  • We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
  • Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
  • Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
  • The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
  • We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
  • The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
  • We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

Ways to contribute:

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M1 Build Date 2026-01-05
  • YP 6.0 M1 Release Date 2026-01-16
  • YP 6.0 M2 Build Date 2026-02-02
  • YP 6.0 M2 Release Date 2026-02-13
  • YP 6.0 M3 Build Date 2026-03-02
  • YP 6.0 M3 Release Date 2026-03-13
  • YP 6.0 M4 Build Date 2026-03-30
  • YP 6.0 M4 Release Date 2026-04-26


Upcoming dot releases:

  • YP 5.0.15 in QA.
  • YP 5.3.1 Build Date 2026-01-12
  • YP 5.3.1 Release Date 2026-01-23
  • YP 4.0.33 Build Date 2026-01-26
  • YP 4.0.33 Release Date 2026-01-30
  • YP 5.0.16 Build Date 2026-02-09
  • YP 5.0.16 Release Date 2026-02-20
  • YP 5.3.2 Build Date 2026-02-16
  • YP 5.3.2 Release Date 2026-02-27
  • YP 4.0.34 Build Date 2026-02-23
  • YP 4.0.34 Release Date 2026-03-06
  • YP 5.3.3 Build Date 2026-03-09
  • YP 5.3.3 Release Date 2026-03-20
  • YP 5.0.17 Build Date 2026-03-16
  • YP 5.0.17 Release Date 2026-03-23
  • YP 4.0.35 Build Date 2026-04-06
  • YP 4.0.35 Release Date 2026-04-17
  • YP 5.3.4 Build Date 2026-04-13
  • YP 5.3.4 Release Date 2026-04-24
  • YP 5.0.18 Build Date 2026-04-20
  • YP 5.0.18 Release Date 2026-05-01
  • YP 5.0.19 Build Date 2026-05-26
  • YP 5.0.19 Release Date 2026-06-05

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=86747"