Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(397 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 27, 2021 ==
== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 3.4 M2<br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: 12th July 2021 YP 3.4 M2 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 July 29th at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Aug. 3rd at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday July 27th at 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)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We plan to build M2 this week once we have pzstd included in the buildtools tarball
*YP 4.0.33 is awaiting approval
*Once M2 is built, 3.3.2 will follow into QA.
*YP 5.0.16 is in QA
*There are proposals to add lz4c, zstd and pzstd as required host commands which we hope will allow better data archiving for license information and possibly for bitbake hash debugging too.
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*There are proposals and discussions on the architecture list around improving the syntax for overrides in the metadata. This would be a major change of a type we haven’t make in a while. The proposal includes the option of allowing the syntax in older bitbake versions to make metadata compatibility easier. Please comment on those discussions on the list if you have opinions on this.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
*The prserv rewrite is still pending on resolving the issues with python asyncio.
**rust do_test_compile/do_install segfault (#16058)
*Intermittent issues are ongoing, particularly ptest ones. Help is very much welcome on these 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
**Generation of releases.json needs updating (#16138)
*The multiconfig changes in bitbake continue to cause problems, we still need simpler test cases to reproduce issues rather than huge builds. The existing patches seem to fix some workloads and break others and current test cases are very slow to work with.
**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:
**“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.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_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.
*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.4 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.4 M2 is out of QA
*WDD 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.4 M3 build date 2021/08/23
*OE-Core/Poky Patch Metrics
*YP 3.4 M3 Release date 2021/09/03
**Total patches found: 1108 (last week 1106)
*YP 3.4 M4 build date 2021/10/04
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
*YP 3.4 M4 Release date 2021/10/29
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Planned upcoming dot releases:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 3.3.2 is being built.
*YP 6.0 M2 Build Date 2026-02-16
*YP 3.3.2 release date 2021/07/30
*YP 6.0 M2 Release Date 2026-02-27
*YP 3.1.10 build date 2021/07/26
*YP 6.0 M3 Build Date 2026-03-09
*YP 3.1.10 release date 2021/08/06
*YP 6.0 M3 Release Date 2026-03-20
*YP 3.1.11 build date 2021/09/13
*YP 6.0 M4 Build Date 2026-03-30
*YP 3.1.11 release date 2021/9/24
*YP 6.0 M4 Release Date 2026-04-26


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2630 (last week 2653) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.16 Release Date 2026-02-20
*Poky Patch Metrics 
*YP 5.3.2 Build Date 2026-02-16
**Total patches found: 1286 (last week 1287)
*YP 5.3.2 Release Date 2026-02-27
**Patches in the Pending State: 486 (38%) [last week 483 (38%)]
*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 48: 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]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 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"