Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(350 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 18th, 2022 ==
== Yocto Project Status 14 April 2026 ==
Current Dev Position: YP 3.5 M2<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: 17th Jan. 2022 YP 3.5 M2 build<br/>
Next Deadline: YP 6.0 M4 Build Date 2026-04-20<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Jan. 20th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Apr. 16th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Feb. 1st at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Apr. 14th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Jan. 18th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 16th 10am GMT and Monday Apr. 20th 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.5 M2 is due to build this week
*YP 5.0.17 is due to be released
*Work has progressed on inclusive language and an email should be out this week about the proposals for that after discussions amongst the volunteers who stepped up to work on it. Some obsolete variables/code have already been removed as a prelude to this.
*YP 6.0 M3 is in QA
*Patches to switch to setuptools and away from distutils following upstream python’s lead have merered (thanks Tim!). Whilst the issues are resolved for core, work remains on other layers such as meta-oe.
*YP 4.0.35 is queued for QA
*The autobuilder does look improved from an intermittent failure perspective but we’re seeing hangs for unknown reasons on debian9 oe-selftest (seems python pthread mutex related) and on ltp on the arm worker. Sadly the open issues are at an all time high.
*We have converted over to sbom-cve-check and dropped cve-check. This has caused a significant increase in CVEs reported, these are being triaged.
*Patches to disable the network outside of do_fetch have merged.
*Issues with pending work needed:
*Support for improved SPDX info for the kernel has merged (thanks Saul).
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
*CVE issues had a bad week with further significant increases for master and stable branches. Some patches have merged to improve master (thanks Ross!).
**Reports of pseudo errors on Fedora 44 beta related to openat2()
*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
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
**Meta-oe cve layer filtering under new tooling (metrics script tweak?)
**Reprodicubility issues with strace/apr-util after gnulib macro changes (patches in testing)
*There was disruption to git services last week due to scraping attacks against the servers. This resulted in connection issues whilst those were mitigated, particularly the git protocol access.
git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*The recent wic changes will need wic support files to be placed in files/wic within layers going forwards.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The final kirkstone build has taken place and we’re no longer planning to merge patches on this branch.
*If you have any final patches for whinlatter, please get these sent to the list ASAP.


'''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.
*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
 
'''Tracking Metrics:'''<br/>
*WDD 2777 (last week 2797) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1072 (last week 1060)
**Patches in the Pending State: 147 (14%) [last week 148 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 3.5 Milestone Dates:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 3.5 M2 build date 2022/01/17
*YP 6.0 M3 in QA.
*YP 3.5 M2 Release date 2022/01/28
*YP 6.0 M4 Build Date 2026-04-13
*YP 3.5 M3 build date 2022/02/21
*YP 6.0 M4 Release Date 2026-05-04
*YP 3.5 M3 Release date 2022/03/04
*YP 3.5 M4 build date 2022/04/04
*YP 3.5 M4 Release date 2022/04/29


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.14 build date 2022/01/24
*YP 5.0.17 is in review.
*YP 3.1.14 Release date 2022/02/04
*YP 4.0.35 is in QA.
*YP 3.4.2 build date 2022/02/07
*YP 5.3.4
*YP 3.4.2 Release date 2022/02/18
**Build Date  2026-04-20
*YP 3.3.5 build date 2022/02/14
**Release Date 2026-05-06
*YP 3.3.5 Release date 2022/02/25
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 3.1.15 build date 2022/03/14
*YP 3.1.15 Release date 2022/03/25
*YP 3.4.3 build date 2022/03/21
*YP 3.4.3 Release date 2022/04/01
*YP 3.3.6 build date 2022/03/28
*YP 3.3.6 Release date 2022/04/08
*YP 3.1.16 build date 2022/04/25
*YP 3.1.16 Release date 2022/05/06
 
'''Tracking Metrics:'''<br/>
*WDD 2675 (last week 2655) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
**Total patches found: 1229 (last week 1234)
**Patches in the Pending State: 345 (28%) [last week 348 (28%)]


'''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 61:


== 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]]

Revision as of 14:47, 14 April 2026

Yocto Project Status 14 April 2026

Current Dev Position: YP 6.0 M4
Next Deadline: YP 6.0 M4 Build Date 2026-04-20

Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 5.0.17 is due to be released
  • YP 6.0 M3 is in QA
  • YP 4.0.35 is queued for QA
  • We have converted over to sbom-cve-check and dropped cve-check. This has caused a significant increase in CVEs reported, these are being triaged.
  • Issues with pending work needed:
    • 32bit x86 kvm seemingly broken with certain CPU features (#16074)
    • Reports of pseudo errors on Fedora 44 beta related to openat2()
    • Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
    • Meta-oe cve layer filtering under new tooling (metrics script tweak?)
    • Reprodicubility issues with strace/apr-util after gnulib macro changes (patches in testing)
  • There was disruption to git services last week due to scraping attacks against the servers. This resulted in connection issues whilst those were mitigated, particularly the git protocol access.

git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.

  • The recent wic changes will need wic support files to be placed in files/wic within layers going forwards.
  • We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
  • The final kirkstone build has taken place and we’re no longer planning to merge patches on this branch.
  • If you have any final patches for whinlatter, please get these sent to the list ASAP.

Ways to contribute:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M3 in QA.
  • YP 6.0 M4 Build Date 2026-04-13
  • YP 6.0 M4 Release Date 2026-05-04

Upcoming dot releases:

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=86805"