Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(95 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 30th, 2024 ==
== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 5.1 M3 <br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: YP 5.1 M3 Build 26 Aug. 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 Aug. 2nd 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 July 30th 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/>
*YP 4.0.20 is due to be released
*YP 5.3.1 was released
*YP 5.1 M2 is in QA
*YP 6.0 M1 was released
*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
*YP 4.0.33 is in QA
*SPDX 3.0 has merged and is now the default.
*YP 6.0 M2 is due to build next week.
*We updated to glibc 2.40, thanks Khem. There is an issue with building pseudo under the new glibc version which is being worked on.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
*We identified an issue which meant warnings/errors in nativesdk recipes were not showing on our autobuilder. We have the fix for the CI issue ready as soon as we fix those warnings/errors, the gcc path problems are proving tricky.
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
*We were able to optimize some space usage in builds, thanks Ross. The results are visible on our performance charts, e.g.: https://autobuilder.yocto.io/pub/non-release/20240723-5/testresults/buildperf-alma8/perf-alma8_master_20240723030045_28fd497a26.html https://autobuilder.yocto.io/pub/non-release/20240723-4/testresults/buildperf-debian11/perf-debian11_master_20240722200022_28fd497a26.html
**rust do_test_compile/do_install segfault (#16058)
*Further help on optimizing build disk usage would be most welcome.
**Generation of releases.json needs updating (#16138)
*Some larger patches still need help with review these would be appreciated:
*Two are currently needing further work:
**Improved CVE tooling from Marta
**x86 kvm broken on Fedora 43 (#16074)
**kernel fitimage changes from Adrian
**AB-INT: opkg-build segmentation fault (#16078)
**bitbake-setup and configuration fragments from Alexander
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*We’ve been trying to resolve some of the longer standing patches in review and are getting more caught up.
*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/>
*YP 4.0.20 was released
*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=---
*YP 5.1 M2 is due to be released
*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/
*A new wiki page summarizing options for meta-gplv2 replacement was created: https://wiki.yoctoproject.org/wiki/Meta-gpl2_layer_replacement (thanks Khem)
*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.
*A document giving a brief overview of the Yocto Project Autobuilder/Infrastructure has been shared: https://wiki.yoctoproject.org/wiki/images/0/04/Yocto_Project_Autobuilder.pdf and will be discussed on today’s engineering sync call.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*Autobuilder intermittent issues continue to cause concern but if we don’t have anyone able to work on them there is little we can do.
 
*A bug in pseudo around the resolution of symlinks was identified and a fix merged, thanks to the reporter for sending a good test case!
'''New to the project?'''<br/>
*We cleaned up a lot of python dependencies and added some extra tests, thanks Ross.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*The rustdoc reproducibility issue was found and fixed, thanks Sundeep! We will now be able to upgrade rust to newer versions although further issues remain in some newer versions.
*The new mesa version requires meta-clang for the intel drivers. We need to make a decision on how to handle this, clang is likely to make its way to core at some point but work is needed to make the overrides suitable for core before that can happen.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2798 (last week 2782) (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: 1083 (last week 1079)
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 179 (16%) [last week 178 (17%)]
**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 M2 is ready for release.
*YP 6.0 M2 Build Date 2026-02-16
*YP 5.1 M3 Build date 2024-08-26
*YP 6.0 M2 Release Date 2026-02-27
*YP 5.1 M3 Release date 2024-09-06
*YP 6.0 M3 Build Date 2026-03-09
*YP 5.1 M4 Build date 2024-09-30
*YP 6.0 M3 Release Date 2026-03-20
*YP 5.1 M4 Release date 2024-10-25
*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.20 is released.
*YP 4.0.33 is in QA.
*YP 5.0.3 Build Date 2024-08-12
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.3 Release Date 2024-08-23
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.21 Build Date 2024-09-09
*YP 5.3.2 Build Date 2026-02-16
*YP 4.0.21 Release Date 2024-09-20
*YP 5.3.2 Release Date 2026-02-27
*YP 5.0.4 Build Date 2024-09-23
*YP 4.0.34 Build Date 2026-02-23
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.34 Release Date 2026-03-06
*YP 4.0.22 Build Date 2024-10-14
*YP 5.3.3 Build Date 2026-03-09
*YP 4.0.22 Release Date 2024-10-25
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.5 Release Date 2024-11-22
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.23 Release Date 2024-11-29
*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 67: 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"