Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(512 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Sept. 1, 2020 ==
== Yocto Project Status 31 March 2026 ==
Current Dev Position: YP 3.2 M3<br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: YP 3.2 M3 build date 2020/8/31 - FEATURE FREEZE<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. 3rd at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting - Thursday Apr. 2nd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Sept. 1st at 8am PDT (https://zoom.us/j/990892712)
*Weekly Project Engineering Sync - Tuesday 31st 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 Apr. 2nd 10am GMT and Monday Apr. 6th 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/>
*YP 3.0.4 was released
*YP 4.0.34 was released.
*M3 is due to close at the end of the week and this is the feature freeze point for 3.2
*YP 5.3.3 is approved for release.
*After much debugging, we’ve concluded the bitbake cooker/server launch process is terminally flawed, you can’t fork a python process into two independent python processes and have the internal python state machinery work correctly. *As such, we’re going to have to make some major changes to the way the bitbake cooker/server startup happens.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*On a positive note, those server changes have forced many of the memory resident bitbake bugs to the surface and the new code appears to fix them, bringing memres bitbake much closer to being usable, maybe even becoming a default in this release if testing goes well.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*There is concern about invasive changes like this with regard to LTS/dunfell where these bitbake bugs are also present. Ultimately we will make a decision about backporting based upon patch stability and user feedback from the LTS users.
*Issues still pending:
*We may delay M3 slightly to enable the bitbake server changes to merge since these are important for release and work making/merging.
**Splitting wic into an external tool.
*The number of autobuilder intermittent bugs has continued to rise unfortunately. 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.
**Converting scripts/run-cvecheck to sbom-cve-check
*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
**DISTRO_FEATURES defaults improvements.
*There is a proposal on the bitbake list to remove globbing support from file:// urls. Usage of these urls currently breaks source file checksumming which users don’t realise, it can’t be fixed in a sane way so and the most common use cases has easy alternatives such as referencing a directory as a file:// url without globs so removing globbing support appears to be the best way forward.
**RHEL 9 xattrs/selinux/tar issue
*We have switched to the 5.8 kernel by default, it's taken a while to get through all the different issues but we appear to be there now, thanks to Bruce for working through many of them!
**How to improve DEBUG_BUILD?
*Some long standing musl SDK issues should be resolved now.
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*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
**Fixing yocto-check-layer to work with --machines (many fixes merged)
*Issues that were resolved this week:
**Sbom-cve-check added
**Replacement of runtlp with kirk (Thanks Daniel!)
**bitbake-setup vscode integration
**Fedora 43 selftest failures
**Reconciling poky and OE-Core defaults templates.
*We have rationalized the tags in various project repositories, more information can be found here: https://lists.openembedded.org/g/openembedded-architecture/message/2312 Whilst controversial, this will make the tag list much easier to understand for users, guide users to use the right tags going forward and remove confusion about whether any tags were “missed”, at the expense that some CI setups may need adjusting short term.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The CFP closing date for the Yocto Project Workshop at Embedded Recipes 2026 has been extended until April 7th, please submit a proposal if you’d like to present: https://pretalx.com/yocto-embedded-recipes-2026/cfp


'''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 2436 (last week 2424) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2814 (last week 2819) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1264 (last week 1273)
**Total patches found: 1062 (last week 1072)
**Patches in the Pending State: 502 (40%) [last week 502 (39%)]
**Patches in the Pending State: 148 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''YP 6.0 Milestone Dates:'''<br/>
*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 was released.
*YP 5.3.3 ready for release.
*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 42: 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:48, 31 March 2026

Yocto Project Status 31 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 4.0.34 was released.
  • YP 5.3.3 is approved for release.
  • 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 still key changes missing.
  • Issues still pending:
    • Splitting wic into an external tool.
    • Converting scripts/run-cvecheck to sbom-cve-check
    • DISTRO_FEATURES defaults improvements.
    • RHEL 9 xattrs/selinux/tar issue
    • How to improve DEBUG_BUILD?
    • RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
  • 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
    • Fixing yocto-check-layer to work with --machines (many fixes merged)
  • Issues that were resolved this week:
    • Sbom-cve-check added
    • Replacement of runtlp with kirk (Thanks Daniel!)
    • bitbake-setup vscode integration
    • Fedora 43 selftest failures
    • Reconciling poky and OE-Core defaults templates.
  • We have rationalized the tags in various project repositories, more information can be found here: https://lists.openembedded.org/g/openembedded-architecture/message/2312 Whilst controversial, this will make the tag list much easier to understand for users, guide users to use the right tags going forward and remove confusion about whether any tags were “missed”, at the expense that some CI setups may need adjusting short term.
  • We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
  • The CFP closing date for the Yocto Project Workshop at Embedded Recipes 2026 has been extended until April 7th, please submit a proposal if you’d like to present: https://pretalx.com/yocto-embedded-recipes-2026/cfp

Ways to contribute:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • 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 was released.
  • YP 5.3.3 ready for release.
  • 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=86796"