Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(32 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Status 3 February 2026 (WW06) ==
== Yocto Project Status 18 August 2026 ==
Current Dev Position: YP 6.0 M2<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-16<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 Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 20th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 18th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 20th Aug. 10am GMT and Monday 24th Aug. 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.3.1 is due to be released
*YP 6.1 M3 is due in two weeks and this will be the feature freeze point for YP 6.1.
*YP 6.0 M1 is in QA
*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.
*YP 4.0.33 is queued for QA after 6.0 M1
*We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*There have been locking changes with do_fetch/do_unpack within the bitbake fetcher to allow better performance of builds with shared DL_DIRs. There are also performance improvements to the handling of repeated ssl connection queries.
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There is discussion on the architecture list about how we could improve the fetcher, particularly around how recursion is handled in git submodules: https://lists.openembedded.org/g/openembedded-architecture/message/2416
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues.
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
*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:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Matchbox-wm segfault/xserver restart
**Generation of releases.json needs updating (#16138)
**aarch64/x86-64 build host contamination/reproducibility issue
*Two are currently needing further work:  
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.
**rust do_test_compile/do_install segfault (#16058)
*Remaining intermittent build failures of concern:
**x86 kvm broken on Fedora 43 (#16074)
**other qemu ‘hang’ type issues on ARM
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
**sometimes yocto-check-layer is showing checksum mismatch issues
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
**intermittent ptest failures in many recipes
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. 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:'''<br/>
'''Ways to contribute:'''<br/>
Line 37: Line 36:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2704 (last week 2694) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Total patches found: 1030 (last week 1028)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**Patches in the Pending State: 139 (14%) [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 Build Date 2026-02-16
*6.1 M3:
*YP 6.0 M2 Release Date 2026-02-27
**Build Date: w/c 2026-08-31
*YP 6.0 M3 Build Date 2026-03-09
**Release Date: w/c 2026-09-14
*YP 6.0 M3 Release Date 2026-03-20
*6.1.0:
*YP 6.0 M4 Build Date 2026-03-30
**Build Date (M4): w/c 2026-10-12
*YP 6.0 M4 Release Date 2026-04-26
**Release Date: w/c 2026-11-02


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.3.1 is under review.
*YP 6.0.3 due to release
*YP 4.0.33 is queued for QA after 6.0 M1.
**Release Date w/c 2026-08-24
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.20
*YP 5.0.16 Release Date 2026-02-20
**Build Date w/c 2026-08-17
*YP 5.3.2 Build Date 2026-02-16
**Release Date w/c 2026-08-31
*YP 5.3.2 Release Date 2026-02-27
*YP 6.0.4
*YP 4.0.34 Build Date 2026-02-23
**Build Date w/c 2026-09-28
*YP 4.0.34 Release Date 2026-03-06
**Release Date w/c 2026-10-12
*YP 5.3.3 Build Date 2026-03-09
*YP 5.0.21
*YP 5.3.3 Release Date 2026-03-20
**Build Date w/c 2026-10-05
*YP 5.0.17 Build Date 2026-03-16
**Release Date w/c 2026-10-19
*YP 5.0.17 Release Date 2026-03-23
 
*YP 4.0.35 Build Date 2026-04-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

Latest revision as of 14:45, 18 August 2026

Yocto Project Status 18 August 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:

  • YP 6.1 M3 is due in two weeks and this will be the feature freeze point for YP 6.1.
  • 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.
  • We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
  • There have been locking changes with do_fetch/do_unpack within the bitbake fetcher to allow better performance of builds with shared DL_DIRs. There are also performance improvements to the handling of repeated ssl connection queries.
  • There is discussion on the architecture list about how we could improve the fetcher, particularly around how recursion is handled in git submodules: https://lists.openembedded.org/g/openembedded-architecture/message/2416
  • We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues.
  • 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:
    • Matchbox-wm segfault/xserver restart
    • aarch64/x86-64 build host contamination/reproducibility issue

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

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 due to release
    • Release Date w/c 2026-08-24
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • 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=86866"