Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(505 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Sept. 8, 2020 ==
== Yocto Project Status 24 March 2026 ==
Current Dev Position: YP 3.2 M3<br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: YP 3.2 M3 Feature Freeze - Now<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Sept. 10th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting - Thursday 26th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Oct. 6th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Project Engineering Sync - Tuesday 24th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Sept. 8th at 8am PDT (https://zoom.us/j/990892712)
*Yocto Project Patch Review - Thursday 26th Mar. 10am GMT and Monday 30th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*M3 has now closed and we’re at feature freeze for 3.2.
*YP 6.0 M2 has been released.
*We now have most patches merged for 3.2, the main remaining question is around the documentation. The current plan is to merge the sphinx branches into master and then build M3.
*YP 4.0.34 is due to be released.
*There is a new technique being used to try and mitigate some of the runtime autobuilder issues, so far the results from that have looked promising (using the runqemu-renice script).
*YP 5.3.3 is in review after QA.
*Some fixes for bitbake’s parsing handling have merged which hopefully will address some of the hung process issues we’ve been seeing. Some of the issues look like potential issues in upstream python multiprocessing.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*There have also been significant cleanups to the server process logging and reporting of processes holding the bitbake lock.
*YP 6.0 M3 is now due to build however there are many key changes needed still missing.  
*The work in enabling PRServ to work well with hash equivalence has merged.
**Issues still pending:
*A preview of the sphinx built documentation is now available at https://docs.yoctoproject.org/, work is ongoing to complete the migration work.
**Splitting wic into an external tool.
*We continue to struggle with a number of autobuilder intermittent bugs. 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 with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
*One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
**How to improve DEBUG_BUILD?
*For older releases, we’ve been struggling to handle these with the changing distros on the autobuilder infrastructure. We’ve managed to pull together various pieces of work to allow these older releases to be built on the infrastructure and an email discussing this was sent to the openembedded-architecture list. It will mean adding some larger series of patches to the older release branches for the yocto-autobuilder-helper and openembedded-core repositories but it is believed this is in the best interests of being able to test these older releases going forward if needed. This may also reduce the barrier to entry for new maintainers and community maintenance.
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
**Fixing yocto-check-layer to work with –machines
*Issues that were resolved this week:
**Switching to pkg-config.
**Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
*We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.


'''YP 3.2 Milestone Dates:'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.2 M3 build date 2020/8/31
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*YP 3.2 M3 Release date 2020/9/11
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*YP 3.2 M4 build date 2020/10/5
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*YP 3.2 M4 Release date 2020/10/30
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 3.1.3 build date 2020/9/14
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 3.1.3 release date 2020/9/25


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2461 (last week 2436) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1264 (last week 1264)
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 502 (40%) [last week 502 (40%)]
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''YP 6.0 Milestone Dates:'''<br/>
*YP 6.0 M2 was released.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04
 
'''Upcoming dot releases:'''<br/>
*YP 4.0.34 ready for release.
*YP 5.3.3 is in review.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*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 41: Line 76:


== 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]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]

Latest revision as of 14:43, 24 March 2026

Yocto Project Status 24 March 2026

Current Dev Position: YP 6.0 M3
Next Deadline: YP 6.0 M3 Build Date 2026-03-23

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0 M2 has been released.
  • YP 4.0.34 is due to be released.
  • YP 5.3.3 is in review after QA.
  • YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
  • YP 6.0 M3 is now due to build however there are many key changes needed still missing.
    • Issues still pending:
    • Splitting wic into an external tool.
    • Deprecation of ltp (upstream dropped runltp and mandate kirk)
    • How to improve DEBUG_BUILD?
    • DISTRO_FEATURES defaults improvements.
    • SBOM/cve-check changes.
    • AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
  • Issues that are mostly known quantities still needing work:
    • x86 kvm seemingly broken with certain CPU features (#16074)
    • Failure to generate regression reports in release builds
    • Reconcile poky and OE-Core defaults templates.
    • Resolve Fedora 43 selftest failures
    • Fixing yocto-check-layer to work with –machines
  • Issues that were resolved this week:
    • Switching to pkg-config.
    • Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
  • We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
  • We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

Ways to contribute:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M2 was released.
  • YP 6.0 M3 Build Date 2026-03-23
  • YP 6.0 M3 Release Date 2026-04-08
  • YP 6.0 M4 Build Date 2026-04-13
  • YP 6.0 M4 Release Date 2026-05-04

Upcoming dot releases:

  • YP 4.0.34 ready for release.
  • YP 5.3.3 is in review.
  • YP 5.0.17 Build Date 2026-03-30
  • YP 5.0.17 Release Date 2026-04-15
  • YP 4.0.35 Build Date 2026-04-06
  • YP 4.0.35 Release Date 2026-04-22
  • YP 5.3.4 Build Date 2026-04-20
  • YP 5.3.4 Release Date 2026-05-06
  • YP 5.0.18 Build Date 2026-04-27
  • YP 5.0.18 Release Date 2026-05-13
  • 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=86794"