Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(59 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Feb. 25th, 2025 ==
== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 5.2 M3<br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.25 is out of QA pending review
*YP 5.3.1 was released
*YP 5.1.3 is in QA
*YP 6.0 M1 was released
*We are now 1 week from feature freeze for 5.2
*YP 4.0.33 is in QA
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*YP 6.0 M2 is due to build next week.
*We are struggling to get stable releases to build cleanly due to intermittent failures, which places strain on everyone. Sadly, traction on help for the intermittent issues remains problematic.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
*There are multiple occasional but annoying autobuilder failures we could do with help debugging/fixing, summarized by https://valkyrie.yocto.io/pub/non-release/abint/
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
**rust do_test_compile/do_install segfault (#16058)
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
**Generation of releases.json needs updating (#16138)
*The newcomer bug list has been triaged and has a number of new issues added.
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review”  - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging 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/>
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*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=---
*There is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
*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/
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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.
*There are bugs that are currently unassigned for YP 5.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_Unassigned_Enhancements/Bugs
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
 
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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.
'''New to the project?'''<br/>
*Help us resolve CVE issues: CVE metrics
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*Ongoing project development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing We need to continue to develop this as it will allow us to potentially find ways to fund specific work items.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2761 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1023 (last week 1030)
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 171 (17%) [last week 172 (17%)]
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.2 Milestone Dates:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 5.2 M3 Build Date 2025-03-03
*YP 6.0 M2 Build Date 2026-02-16
*YP 5.2 M3 Release Date 2025-03-14
*YP 6.0 M2 Release Date 2026-02-27
*YP 5.2 M4 Build Date 2025-03-31
*YP 6.0 M3 Build Date 2026-03-09
*YP 5.2 M4 Release Date 2025-04-25
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.25 is in review.
*YP 4.0.33 is in QA.
*YP 5.1.3 is in QA.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.8 Build Date 2025-03-10
*YP 5.0.16 Release Date 2026-02-20
*YP 5.0.8 Release Date 2025-03-21
*YP 5.3.2 Build Date 2026-02-16
*YP 5.1.4 Build Date 2025-03-24
*YP 5.3.2 Release Date 2026-02-27
*YP 5.1.4 Release Date 2025-04-04
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.34 Release Date 2026-03-06
*YP 4.0.26 Release Date 2025-04-18
*YP 5.3.3 Build Date 2026-03-09
*YP 5.0.9 Build Date 2025-04-21
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.9 Release Date 2025-05-02
*YP 5.0.17 Build Date 2026-03-16
*YP 4.0.27 Build Date 2025-05-19
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.27 Release Date 2025-05-30
*YP 4.0.35 Build Date 2026-04-06
*YP 5.0.10 Build Date 2025-06-02
*YP 4.0.35 Release Date 2026-04-17
*YP 5.0.10 Release Date 2025-06-13
*YP 5.3.4 Build Date 2026-04-13
*YP 4.0.28 Build Date 2025-06-30
*YP 5.3.4 Release Date 2026-04-24
*YP 4.0.28 Release Date 2025-07-11
*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/>
Line 65: Line 79:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]

Latest revision as of 15:43, 10 February 2026

Yocto Project Status 10 February 2026

Current Dev Position: YP 6.0 M2
Next Deadline: YP 6.0 M2 Build Date 2026-02-16

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.3.1 was released
  • YP 6.0 M1 was released
  • YP 4.0.33 is in QA
  • YP 6.0 M2 is due to build next week.
  • There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
    • Issues reusing binaries from fedora 42/43 on older systems (#16087)
    • rust do_test_compile/do_install segfault (#16058)
    • Generation of releases.json needs updating (#16138)
  • Two are currently needing further work:
    • x86 kvm broken on Fedora 43 (#16074)
    • AB-INT: opkg-build segmentation fault (#16078)
  • We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
  • The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
  • Patch review is now using two branches:
  • Patches are merging 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:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M2 Build Date 2026-02-16
  • YP 6.0 M2 Release Date 2026-02-27
  • YP 6.0 M3 Build Date 2026-03-09
  • YP 6.0 M3 Release Date 2026-03-20
  • YP 6.0 M4 Build Date 2026-03-30
  • YP 6.0 M4 Release Date 2026-04-26

Upcoming dot releases:

  • YP 4.0.33 is in QA.
  • YP 5.0.16 Build Date 2026-02-09
  • YP 5.0.16 Release Date 2026-02-20
  • YP 5.3.2 Build Date 2026-02-16
  • YP 5.3.2 Release Date 2026-02-27
  • YP 4.0.34 Build Date 2026-02-23
  • YP 4.0.34 Release Date 2026-03-06
  • YP 5.3.3 Build Date 2026-03-09
  • YP 5.3.3 Release Date 2026-03-20
  • YP 5.0.17 Build Date 2026-03-16
  • YP 5.0.17 Release Date 2026-03-23
  • YP 4.0.35 Build Date 2026-04-06
  • 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:
https://wiki.yoctoproject.org/wiki/TSC

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86767"