Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
m (Typo dashbard -> dashboard)
No edit summary
 
(28 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 3 March 2026 ==
== Yocto Project Status 8 September 2026 ==
Current Dev Position: YP 6.0 M3<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-09<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 10th Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 8st Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 10th Sept. 10am GMT and Monday 14th Sept. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.33 has been released
* YP 5.0.20 is under review.
*YP 5.0.16 is in TSC review
* YP 6.1 M3 is due to build and we are at feature freeze
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
* There are issues with changes in bot/AI protection at github.com which are affecting our CI.  
**We are aware of changes in QA timelines and are discussing how to address them.
* Most M3 changes have merged, we want to mitigate the github issues before building M3.
*We have issues which need further work that will block M3:
* There is a new meta-openjdk layer: https://github.com/amarula/meta-openjdk https://lore.kernel.org/yocto-patches/xBB4.1788187111192557019.ULaN@lists.yoctoproject.org/T/#u
**x86 kvm seemingly broken with certain CPU features (#16074)
* AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
* There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**Failure to generate regression reports in release builds
** Matchbox-wm segfault/xserver restart
*We also have issues we need to resolve before release:
** aarch64/x86-64 build host contamination/reproducibility issue
**Allowing non-destructive git fetcher updates for bitbake-setup.
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
**Splitting wic into an external tool.
*Remaining intermittent build failures of concern:
**Kernel rust support.
**other qemu ‘hang’ type issues on ARM
**Switching to pkg-config.
**sometimes yocto-check-layer is showing checksum mismatch issues
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**intermittent ptest failures in many recipes
**How to improve DEBUG_BUILD?
*Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 43: Line 37:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2622 (last week 2612) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 11063 (last week 1107)
**Total patches found: 1050 (last week 1039)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**Patches in the Pending State: 136 (13%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 6.0 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 6.0 M2 is in QA.
*6.1 M3:
*YP 6.0 M3 Build Date 2026-03-09
**Build Date: w/c 2026-08-31
*YP 6.0 M3 Release Date 2026-03-20
**Release Date: w/c 2026-09-14
*YP 6.0 M4 Build Date 2026-03-30
*6.1.0:
*YP 6.0 M4 Release Date 2026-04-26
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.16 is in review.
*YP 6.0.3 is in review.
*YP 5.3.2 is in QA.
**Release Date w/c 2026-08-24
*YP 4.0.34 is in QA.
*YP 5.0.20 is in QA.
*YP 5.3.3 Build Date 2026-03-09
**Release Date w/c 2026-08-31
*YP 5.3.3 Release Date 2026-03-20
*YP 6.0.4
*YP 5.0.17 Build Date 2026-03-16
**Build Date w/c 2026-09-28
*YP 5.0.17 Release Date 2026-03-23
**Release Date w/c 2026-10-12
*YP 4.0.35 Build Date 2026-04-06
*YP 5.0.21
*YP 4.0.35 Release Date 2026-04-17
**Build Date w/c 2026-10-05
*YP 5.3.4 Build Date 2026-04-13
**Release Date w/c 2026-10-19
*YP 5.3.4 Release Date 2026-04-24
 
*YP 5.0.18 Build Date 2026-04-20
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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/>

Latest revision as of 14:41, 8 September 2026

Yocto Project Status 8 September 2026

Current Dev Position: YP 6.1 M3
Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:

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

Key Status/Updates:

We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.

  • Remaining intermittent build failures of concern:
    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • intermittent ptest failures in many recipes
  • Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M3:
    • Build Date: w/c 2026-08-31
    • Release Date: w/c 2026-09-14
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 6.0.3 is in review.
    • Release Date w/c 2026-08-24
  • YP 5.0.20 is in QA.
    • Release Date w/c 2026-08-31
  • YP 6.0.4
    • Build Date w/c 2026-09-28
    • Release Date w/c 2026-10-12
  • YP 5.0.21
    • Build Date w/c 2026-10-05
    • Release Date w/c 2026-10-19

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