Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(328 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Feb. 23rd, 2022 ==
== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 3.5 M4<br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: 4th Apr. 2022 YP 3.5 M4 build<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 Feb. 25th 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)
*Monthly Project Meeting Tuesday Mar. 1st 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)
*Weekly Engineering Sync Tuesday Feb. 23rd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Feb. 10am GMT and Monday 16th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now at feature freeze for 3.5, our next LTS release
*YP 5.3.1 was released
*YP 3.1.14 and YP 3.2.4 were released
*YP 6.0 M1 was released
*YP 3.3.5 is in QA
*YP 4.0.33 is in QA
*After a last minute push, the base set of inclusive language changes have merged. There is a conversion script which can be run to convert layers. Not all changes needed have been written yet but enough are present to allow the conversion process to start.
*YP 6.0 M2 is due to build next week.
*There were also changes to convert LICENSE fields to use SPDX identifiers and there is a second conversion script for this that can be used.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
*We have updated the core layer series name to kirkstone and other layers will now need to update to confirm compatibility with kirkstone.
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
*There is a patchset to update python’s build processes to use the upstream preferred wheel approach which would aid support of python over the next few years. It is late in the cycle for this kind of change but we will give this series a few days of testing to make a decision and welcome user feedback either way on these changes.
**rust do_test_compile/do_install segfault (#16058)
*As such, the M3 release build will likely not happen until early next week.
**Generation of releases.json needs updating (#16138)
*The autobuilder infrastructure is planned to be offline 26-28th February for a data center move. Public services like the website, wiki and git servers will remain live but the git backend (push.yoctoproject.org) will be offline, as will the downloads and sstate services and the autobuilder/NAS.
*Two are currently needing further work:
*Capacity has been improved on the sstate server which was causing intermittent timeout issues for downloads.
**x86 kvm broken on Fedora 43 (#16074)
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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 In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.
**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/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 that are currently unassigned for YP 3.5. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhancements.2FBugs
*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/
*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.
*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.
*Help us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
 
'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 3.5 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.5 M3 build date 2022/02/21
*WDD 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.5 M3 Release date 2022/03/04
*OE-Core/Poky Patch Metrics
*YP 3.5 M4 build date 2022/04/04
**Total patches found: 1106 (last week 1100)
*YP 3.5 M4 Release date 2022/04/29
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**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/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.14 is released
*YP 4.0.33 is in QA.
*YP 3.4.2 is released
*YP 5.0.16 Build Date 2026-02-09
*YP 3.3.5 is in QA
*YP 5.0.16 Release Date 2026-02-20
*YP 3.3.5 Release date 2022/02/25
*YP 5.3.2 Build Date 2026-02-16
*YP 3.1.15 build date 2022/03/14
*YP 5.3.2 Release Date 2026-02-27
*YP 3.1.15 Release date 2022/03/25
*YP 4.0.34 Build Date 2026-02-23
*YP 3.4.3 build date 2022/03/21
*YP 4.0.34 Release Date 2026-03-06
*YP 3.4.3 Release date 2022/04/01
*YP 5.3.3 Build Date 2026-03-09
*YP 3.3.6 build date 2022/03/28
*YP 5.3.3 Release Date 2026-03-20
*YP 3.3.6 Release date 2022/04/08
*YP 5.0.17 Build Date 2026-03-16
*YP 3.1.16 build date 2022/04/25
*YP 5.0.17 Release Date 2026-03-23
*YP 3.1.16 Release date 2022/05/06
*YP 4.0.35 Build Date 2026-04-06
 
*YP 4.0.35 Release Date 2026-04-17
'''Tracking Metrics:'''<br/>
*YP 5.3.4 Build Date 2026-04-13
*WDD 2652 (last week 2662) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.3.4 Release Date 2026-04-24
*Poky Patch Metrics
*YP 5.0.18 Build Date 2026-04-20
**Total patches found: 1202 (last week 1208)
*YP 5.0.18 Release Date 2026-05-01
**Patches in the Pending State: 334 (28%) [last week 334 (28%)]
*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 58: Line 79:


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