Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(16 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Status 2 June 2026 ==
== Yocto Project Status 22 September 2026 ==
Current Dev Position: YP 6.1 M1<br/>
Current Dev Position: YP 6.1 M4 - Stabilization (Bug Fixing)<br/>
Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>
Next Deadline: YP 6.1 M4: w/c 2026-10-12<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 4th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 24th Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 2nd June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 22nd Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 4th June 10am GMT and Monday 8th June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 24th Sept. 10am GMT and Monday 28th 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 5.0.18 is due to be released
*YP 5.0.20 was released
*YP 6.0.1 is in QA.
*YP 6.1 M3 is due for release
*YP 6.1 M1 is due to build next week
*Our plan is to build M4 within the next week unless significant problems become known as we’re not aware of anyone working on any major fixes which would delay it.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*If there are release blocking issues, please report ASAP.
*The upgrade to gcc 16 merged
*We have made progress on the build architecture reproducibility issues, thanks in particular to Alejandro and Sunil and team at Windriver for getting the major rust issues resolved. There are around 30 issues left as shown by the *autobuilder tests (down from ~90) so great progress.
*We are planning to improve our python subprocess calls to avoid shell=True, we would appreciate others following and doing this in their code too.
*python3-six recipe moved to meta-oe, it provides python 2.x era support so nothing should be needing that now - references are a sign that dependencies probably need updating but it is still available if needed.
*Intermittent build failures continue to be problematic and unchanged from last week:
*There are issues which are in a position where others could now help:
**several qemu ‘hang’ type issues
**Matchbox-wm segfault/xserver restart
**sometimes yocto-check-layer is showing checksum mismatch issues
**aarch64/x86-64 build host contamination/reproducibility issue - thanks for the work and fixes so far on this.
**siggen reset issues (“ResourceWarning: unclosed transport”)
**See Richard’s email on the list https://lists.openembedded.org/g/openembedded-core/topic/areas_we_could_do_with/121159956 which details some others too
**groff build race issues
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.
**intermittent ptest failures in many recipes
*Qemu v11 dropped support for 32 bit hosts and we are likely to drop support for running builds on 32 bits hosts
*The upstream kernel is looking likely to drop x32 support and if they do, we will have to drop our support too - let hem/us know if you’re using it!
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto


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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2630 (last week 2660) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2640 (last week 2647) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 108 (last week 1083)
**Total patches found: 1055 (last week 1054)
**Patches in the Pending State: 147 (14%) [last week 148 (13%)]
**Patches in the Pending State: 137 (13%) [last week 135 (1%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3
7
 
'''Upcoming development releases:'''<br/>
*6.1 M3: is due for release
*6.1.0:
**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.18 is in review.
*YP 5.0.20 was released
*YP 6.0.1 is in QA.
*YP 6.0.4
*YP 6.0.2
**Build Date w/c 2026-09-28
**Build Date 2026-06-23
**Release Date w/c 2026-10-12
**Release Date 2026-07-06
*YP 5.0.21
*YP 5.0.19
**Build Date w/c 2026-10-05
**Build Date 2026-06-30
**Release Date w/c 2026-10-19
**Release Date 2026-07-13
 
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar



Latest revision as of 14:45, 22 September 2026

Yocto Project Status 22 September 2026

Current Dev Position: YP 6.1 M4 - Stabilization (Bug Fixing)
Next Deadline: YP 6.1 M4: w/c 2026-10-12

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.20 was released
  • YP 6.1 M3 is due for release
  • Our plan is to build M4 within the next week unless significant problems become known as we’re not aware of anyone working on any major fixes which would delay it.
  • If there are release blocking issues, please report ASAP.
  • We have made progress on the build architecture reproducibility issues, thanks in particular to Alejandro and Sunil and team at Windriver for getting the major rust issues resolved. There are around 30 issues left as shown by the *autobuilder tests (down from ~90) so great progress.
  • python3-six recipe moved to meta-oe, it provides python 2.x era support so nothing should be needing that now - references are a sign that dependencies probably need updating but it is still available if needed.
  • There are issues which are in a position where others could now help:

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.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M3: is due for release
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 5.0.20 was released
  • 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