Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(105 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 18th, 2024 ==
== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 5.1 M2 <br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<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 June 13th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 12th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday June 11th at 8 am PDT (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/>
* Both YP 4.0.19 and YP 5.1 M1 have been through QA and will be released shortly
*YP 5.3.1 was released
* Patch status tags are now checked for my default. Layers which don't wish this can disable it.
*YP 6.0 M1 was released
* Fedora 40 support should be almost complete, last issue I'm aware of is in 'expect'
*YP 4.0.33 is in QA
* Some larger patches are on the list and help reviewing these would be appreciated:
*YP 6.0 M2 is due to build next week.
** SPDX 3.0 from Joshua
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
** CVE tooling from Marta
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
** bitbake-setup and configuration fragments from Alexander
**rust do_test_compile/do_install segfault (#16058)
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
**Generation of releases.json needs updating (#16138)
*Please consider signing this to show support for those changes. Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
*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 are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_Unassigned_Enhancements/Bugs
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*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.
 
*Help us resolve CVE issues: CVE metrics
'''New to the project?'''<br/>
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2774 (last week 2772) (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: 1072 (last week 1098)
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 205 (19%) [last week 205 (19%)]
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 5.1 M1 is in QA
*YP 6.0 M2 Build Date 2026-02-16
*YP 5.1 M1 Release date 2024-05-31
*YP 6.0 M2 Release Date 2026-02-27
*YP 5.1 M2 Build date 2024-07-08
*YP 6.0 M3 Build Date 2026-03-09
*YP 5.1 M2 Release date 2024-07-19
*YP 6.0 M3 Release Date 2026-03-20
*YP 5.1 M3 Build date 2024-08-26
*YP 6.0 M4 Build Date 2026-03-30
*YP 5.1 M3 Release date 2024-09-06
*YP 6.0 M4 Release Date 2026-04-26
*YP 5.1 M4 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.19 is ready for release.
*YP 4.0.33 is in QA.
*YP 5.0.2 Build Date 2024-06-24
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.2 Release Date 2024-07-05
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.20 Build Date 2024-07-15
*YP 5.3.2 Build Date 2026-02-16
*YP 4.0.20 Release Date 2024-07-26
*YP 5.3.2 Release Date 2026-02-27
*YP 5.0.3 Build Date 2024-08-12
*YP 4.0.34 Build Date 2026-02-23
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.34 Release Date 2026-03-06
*YP 4.0.21 Build Date 2024-09-09
*YP 5.3.3 Build Date 2026-03-09
*YP 4.0.21 Release Date 2024-09-20
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.4 Release Date 2024-10-04
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.22 Release Date 2024-10-25
*YP 4.0.35 Release Date 2026-04-17
*YP 5.0.5 Build Date 2024-11-11
*YP 5.3.4 Build Date 2026-04-13
*YP 5.0.5 Release Date 2024-11-22
*YP 5.3.4 Release Date 2026-04-24
*YP 4.0.23 Build Date 2024-11-18
*YP 5.0.18 Build Date 2026-04-20
*YP 4.0.23 Release Date 2024-11-29
*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 68: Line 79:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 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"