Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(81 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Oct. 8th,  2024 ==
== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 5.1 release built and awaiting release notes<br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: YP 5.1 M4 Release date 2024-10-25<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 Oct. 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Oct. 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd 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 5.0.4 is due to be released
*YP 4.0.33 is awaiting approval
*YP 5.1 rc1 (final release) is out of QA, the final work item is updating the documentation. Help to write and review release notes and migration guides is greatly appreciated.
*YP 5.0.16 is in QA
*The situation with Fedora 41 and python 3.13 has improved. There are several bitbake fixes needed and one one for pseudo the posix_spawn function.
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*The bb.exceptions module could use some attention from someone with appropriate python knowledge (it makes tracebacks pickleable).
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
*CVE emails are now reporting correctly again, thanks Steve.
**rust do_test_compile/do_install segfault (#16058)
*We can now compare the performance of the new autobuilder perf builds:
**Generation of releases.json needs updating (#16138)
**https://autobuilder.yocto.io/pub/non-release/20241007-108/testresults/buildperf-alma8/perf-alma8_master_20241007210052_312488228a.html
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
**https://valkyrie.yocto.io/pub/non-release/20241008-2/testresults/buildperf-alma8/perf-alma8-vk_master_20241008030040_312488228a.html
*Two are currently needing further work:
*The performance workers are about twice the speed (but the performance workers were not normal worker nodes on the old system). rm_work adds about a minute to build times on a modern SSD system.
**x86 kvm broken on Fedora 43 (#16074)
*Migration to the new autobuilder is proceeding with regular users now encouraged to trigger builds on the new cluster to stress test and identify any issues.
**AB-INT: opkg-build segmentation fault (#16078)
*We are having problems with the toaster tests failing after layer index updates for styhead. If anyone has knowledge of selenium CSS selectors we’d appreciate assistance!
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*For 5.2 it would be helpful to have rough development plans for areas of the project if anyone is able to help document a rough roadmap/plan for them. The following areas are known to be being or need working on:
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
**Autobuilder
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
**Binary Distro
*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.
**Bitbake config fragments
*Patch review is now using two branches:
**Bitbake setup process/tooling
**“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)
**GUI screen shot QA test
**“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)
**IDE Plugin development
*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.
**Layer Index
**Patchtest
**Security Tooling
**Swatbot
**Toaster
*If there are other areas we should have plans for, please let us know.


'''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.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2704 (last week 2749) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1067 (last week 1067)
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 176 (16%) [last week 176 (16%)]
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 M4 Release date 2024-10-25


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


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.4 is due to be released.
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.22 Build Date 2024-10-14
*YP 5.3.2 Build Date 2026-02-16
*YP 4.0.22 Release Date 2024-10-25
*YP 5.3.2 Release Date 2026-02-27
*YP 5.0.5 Build Date 2024-11-11
*YP 4.0.34 Build Date 2026-02-23
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.34 Release Date 2026-03-06
*YP 4.0.23 Build Date 2024-11-18
*YP 5.3.3 Build Date 2026-03-09
*YP 4.0.23 Release Date 2024-11-29
*YP 5.3.3 Release Date 2026-03-20
*YP 5.1.1 Build Date 2024-12-02  
*YP 5.0.17 Build Date 2026-03-16
*YP 5.1.1 Release Date 2024-12-13
*YP 5.0.17 Release Date 2026-03-23
*YP 5.0.6 Build Date 2024-12-16  
*YP 4.0.35 Build Date 2026-04-06
*YP 5.0.6 Release Date 2024-12-27
*YP 4.0.35 Release Date 2026-04-17
*YP 4.0.24 Build Date 2025-01-06
*YP 5.3.4 Build Date 2026-04-13
*YP 4.0.24 Release Date 2025-01-17
*YP 5.3.4 Release Date 2026-04-24
*YP 5.1.2 Build Date 2025-01-13
*YP 5.0.18 Build Date 2026-04-20
*YP 5.1.2 Release Date 2025-01-24
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.7 Build Date 2025-01-27
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.7 Release Date 2025-02-07
*YP 5.0.19 Release Date 2026-06-05
*YP 4.0.25 Build Date 2025-02-17
*YP 4.0.25 Release Date 2025-02-28
*YP 5.1.3 Build Date 2025-02-24
*YP 5.1.3 Release Date 2025-03-07
*YP 5.0.8 Build Date 2025-03-10
*YP 5.0.8 Release Date 2025-03-21
*YP 5.1.4 Build Date 2025-03-24
*YP 5.1.4 Release Date 2025-04-04
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.26 Release Date 2025-04-18
*YP 5.0.9 Build Date 2025-04-21
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.0.10 Build Date 2025-06-02
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11


'''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 105: Line 77:


== 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:56, 17 February 2026

Yocto Project Status 17 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 4.0.33 is awaiting approval
  • YP 5.0.16 is in QA
  • YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
  • There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
    • rust do_test_compile/do_install segfault (#16058)
    • Generation of releases.json needs updating (#16138)
    • AB-INT: do_image_wic: tar command return exit status 2 (#16143)
  • Two are currently needing further work:
    • x86 kvm broken on Fedora 43 (#16074)
    • AB-INT: opkg-build segmentation fault (#16078)
  • We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
  • We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
  • We removed legacy tls support from openssl in the interests of providing better secure defaults.
  • 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 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