Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(433 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Mar. 23, 2021 ==
== Yocto Project Status 3 February 2026 (WW06) ==
Current Dev Position: YP 3.3 M4 (Feature Freeze)<br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: 5th April 2021 YP 3.3 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 Mar. 25th at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Apr. 6th at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Mar. 23rd at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th 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/>
*YP 3.3 M3 has been built and is now in QA.
*YP 5.3.1 is due to be released
*We were able to track down the parsing performance regressions and patches in master have addressed those (thanks Peter).
*YP 6.0 M1 is in QA
*We have merged REQUIRED_VERSION support to bitbake which works in a similar way to PREFERRED_VERSION but is a mandatory directive rather than optional.
*YP 4.0.33 is queued for QA after 6.0 M1
*Reproducibility has improved again with ltp fixed, perf fixed and fixes pending for meson and ovmf. This leaves ruby-docs and the Go Language issues, https://www.yoctoproject.org/reproducible-build-results/
*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).
*qemuppc64 and qemuriscv32 machines were added. These are not officially supported/tested but have been added to oe-core to allow development to focus around them rather than happening ad hoc externally. For official support of these platforms there would need to be some funding for the autobuilder resources needed through project members sponsoring that work.
*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.
*A new Azure Storage fetcher was added to bitbake.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
*“Pending” state patch review is still needed, we have some really old stale ones which really need decisions to be made about their future. It would help a lot if recipe maintainers could review recipe patchsets and upstream them or remove them if they are no longer relevant.
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
*Intermittent autobuilder issues continue to occur and are now at a record high level. 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 We are working to identify the load pattern on the infrastructure that seems to trigger these. We have seen a sharp rise in numbers of issues with the new more rigorous swat process.
**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:'''<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.3 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.3 M3 is being reviewed for release.
*WDD 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.3 M4 build date 2021/04/05
*OE-Core/Poky Patch Metrics
*YP 3.3 M4 Release date 2021/04/30
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Planned upcoming dot releases:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 3.2.3 build date 2021/03/22
*YP 6.0 M2 Build Date 2026-02-16
*YP 3.2.3 release date 2021/04/02
*YP 6.0 M2 Release Date 2026-02-27
*YP 3.1.7 build date 2021/03/29
*YP 6.0 M3 Build Date 2026-03-09
*YP 3.1.7 release date 2021/04/09
*YP 6.0 M3 Release Date 2026-03-20
*YP 3.2.4 build date 2021/05/3
*YP 6.0 M4 Build Date 2026-03-30
*YP 3.2.4 release date 2021/05/14
*YP 6.0 M4 Release Date 2026-04-26
*YP 3.1.8 build date 2021/05/17
*YP 3.1.8 release date 2021/05/28


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2748 (last week 2759) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.3.1 is under review.
*Poky Patch Metrics 
*YP 4.0.33 is queued for QA after 6.0 M1.
**Total patches found: 1309 (last week 1319)
*YP 5.0.16 Build Date 2026-02-09
**Patches in the Pending State: 492 (38%) [last week 489 (37%)]
*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 49: 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 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"