Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(71 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Nov. 26th, 2024 ==
== Yocto Project Status 3 February 2026 (WW06) ==
Current Dev Position: YP 5.2 M1<br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: YP 5.2 M1 Release date 2024-12-09<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 Nov. 28th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Nov. 26th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th 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.5 was released.
*YP 5.3.1 is due to be released
*YP 4.0.23 is in under review.
*YP 6.0 M1 is in QA
*Patch merging is continuing to flow but there are a lot of upgrades pending that were recently posted.
*YP 4.0.33 is queued for QA after 6.0 M1
*BB_DANGLINGAPPENDS_WARNONLY was removed.
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*yocto-check-layer is now checking for SECURITY files and there are changes planned for increasing the QA checks tested for.
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*The yocto-testresults repository was reworked and the commits recreated to avoid problems with the size of the repository. The log files were separated to an http share here: https://valkyrie.yocto.io/pub/non-release/testresult-logarchives/
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
*These changes pose a question/challenge for the stable branches. The changes mean we should avoid breaking git mirroring.
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
*As a result of this work, the reproducible builds summary page now functions much faster.
**Hangs of the autobuilder controller (database locking?) (#16129)
*Several performance tweaks were made for bitbake pipe handling for large amounts of log data to avoid slow ptest builds and hangs.
**Generation of releases.json needs updating (#16138)
*A potential new “include_all” conf file directive (discussed on the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2055 ) has no strong objections and is proceeding to proof of concept
*Two are currently needing further work:
*There are patches under review for the addition of configuration fragment management to bitbake. It does require the addition of support for ‘/’ characters in variable flag names (which has been requested in the past too).
**rust do_test_compile/do_install segfault (#16058)
*The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
**x86 kvm broken on Fedora 43 (#16074)
*We need to continue to develop this, thanks to all who have contributed so far!
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again 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.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2736 (last week 2721) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1073 (last week 1077)
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 178 (17%) [last week 178 (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 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.5 was released.
*YP 5.3.1 is under review.
*YP 4.0.23 is in review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 4.0.23 Release Date 2024-11-29
*YP 5.0.16 Build Date 2026-02-09
*YP 5.1.1 Build Date 2024-12-02  
*YP 5.0.16 Release Date 2026-02-20
*YP 5.1.1 Release Date 2024-12-13
*YP 5.3.2 Build Date 2026-02-16
*YP 5.0.6 Build Date 2024-12-16  
*YP 5.3.2 Release Date 2026-02-27
*YP 5.0.6 Release Date 2024-12-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.34 Release Date 2026-03-06
*YP 4.0.24 Release Date 2025-01-17
*YP 5.3.3 Build Date 2026-03-09
*YP 5.1.2 Build Date 2025-01-13
*YP 5.3.3 Release Date 2026-03-20
*YP 5.1.2 Release Date 2025-01-24
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.7 Build Date 2025-01-27
*YP 5.0.17 Release Date 2026-03-23
*YP 5.0.7 Release Date 2025-02-07
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.25 Build Date 2025-02-17
*YP 4.0.35 Release Date 2026-04-17
*YP 4.0.25 Release Date 2025-02-28
*YP 5.3.4 Build Date 2026-04-13
*YP 5.1.3 Build Date 2025-02-24
*YP 5.3.4 Release Date 2026-04-24
*YP 5.1.3 Release Date 2025-03-07
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.8 Build Date 2025-03-10
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.8 Release Date 2025-03-21
*YP 5.0.19 Build Date 2026-05-26
*YP 5.1.4 Build Date 2025-03-24
*YP 5.0.19 Release Date 2026-06-05
*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 87: 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 14:04, 3 February 2026

Yocto Project Status 3 February 2026 (WW06)

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 is due to be released
  • YP 6.0 M1 is in QA
  • YP 4.0.33 is queued for QA after 6.0 M1
  • YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
  • Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
  • There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
    • Issues reusing binaries from fedora 42/43 on older systems (#16087)
    • Hangs of the autobuilder controller (database locking?) (#16129)
    • Generation of releases.json needs updating (#16138)
  • Two are currently needing further work:
    • rust do_test_compile/do_install segfault (#16058)
    • x86 kvm broken on Fedora 43 (#16074)
  • “build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
  • The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
  • Patches are merging again 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.3.1 is under review.
  • YP 4.0.33 is queued for QA after 6.0 M1.
  • 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=86763"