Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(164 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status October 3rd, 2023 ==
== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 4.3 M4 (Feature Freeze)<br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: 2nd October 2023 YP 4.3 M4 build date<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>


'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday October 5th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday October 3rd 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.3 M4 is due to build this week. We have challenges due to the kernel version.
*YP 4.0.33 is awaiting approval
*YP 3.1.28 was released.
*YP 5.0.16 is in QA
*YP 4.0.13 is due to be released
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*The biggest challenge for the M4 build is that the 6.4 kernel was made EOL. Thanks to hard work from Bruce we have 6.5 recipes but this kernel version is throwing multiple errors in testing:
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**cryptodev breaks (patch in master-next)
**rust do_test_compile/do_install segfault (#16058)
**x86 image testing randomly fails with login issues (both selftest and testimage)
**Generation of releases.json needs updating (#16138)
**arm kvm ptest images randomly throw jitterentropy errors and fail
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
**strace ptest failures (x86 and arm)
*Two are currently needing further work:
**arm LTP testing fails with OOM crashes
**x86 kvm broken on Fedora 43 (#16074)
We don’t have fixes for the OOM issue or strace at this point, potential ideas for other issues are undergoing testing.
**AB-INT: opkg-build segmentation fault (#16078)
*The numpy reproducibility issue was finally root caused and resolved.
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*Issues with mesa-native and contamination with llvm from the host have been resolved
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*Improvements to bitbake-getvar output and handling of undefined values were merged
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The openssh ptest intermittent failure does have better logs available but we’ve yet to decode what it means:
*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.
http://autobuilder.yocto.io/pub/non-release/20230917-2/testresults/qemuarm64-ptest/openssh.log
*Patch review is now using two branches:
*The project is working on improving its security processes and policies, there are emails on the mailing list discussing this. Please highlight these to any parties who may be interested or have useful feedback.
**“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: patchtest, layerindex, 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 4.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_Unassigned_Enhancements.2FBugs
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
 
'''YP 4.3 Milestone Dates:'''<br/>
*YP 4.3 M3 was released.
*YP 4.3 M4 build date  2023/10/02
*YP 4.3 M4 Release date 2023/10/27
 
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M1 build date 2023/12/04
*YP 5.0 M1 Release date 2023/12/15
*YP 5.0 M2 build date  2024/01/15
*YP 5.0 M2 Release date 2024/01/24
*YP 5.0 M3 build date  2024/02/19
*YP 5.0 M3 Release date 2024/03/01
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30


'''Upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 3.1.28 is ready for release.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 4.0.13 is in QA.
*YP 3.1.29 build date 2023/10/30
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.14 build date 2023/11/06
*YP 4.0.14 Release date 2023/11/17
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*YP 4.3.1 build date 2023/11/27
*YP 4.3.1 Release date 2023/12/08
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29
*YP 4.3.2 build date 2024/01/08
*YP 4.3.2 Release date 2024/01/19
*YP 3.1.31 build date 2024/01/22
*YP 3.1.31 Release date 2024/02/02
*YP 4.0.16 build date 2024/01/29
*YP 4.0.16 Release date 2024/02/09
*YP 4.3.3 build date 2024/02/12
*YP 4.3.3 Release date 2024/02/23
*YP 3.1.32 build date 2024/03/04
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.17 build date 2024/03/11
*YP 4.0.17 Release date 2024/03/22
*YP 4.3.4 build date 2024/03/25
*YP 4.3.4 Release date 2024/04/05
*YP 3.1.33 build date 2024/04/15
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.18 build date 2024/04/22
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.19 build date 2024/06/03
*YP 4.0.19 Release date 2024/06/14


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2455 (last week 2475) (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: 1176 (last week 1183)
**Total patches found: 1108 (last week 1106)
*Patches in the Pending State: 254 (21%) [last week 254 (21%)]
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''YP 6.0 Milestone Dates:'''<br/>
*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:'''<br/>
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 100: Line 77:


== 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]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 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

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