Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(201 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 20th, 2023 ==
== Yocto Project Status 14 April 2026 ==
Current Dev Position: YP 4.3 M2<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: 17th July 2023 YP 4.3 M2 build date<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 June 22nd 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)
*Weekly Engineering Sync Tuesday June 20th 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)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Apr. 16th 10am GMT and Monday Apr. 20th 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.3 M1 was released
*YP 5.0.17 is due to be released
*YP 3.1.26 is in QA
*YP 6.0 M3 is in QA
*The project has some exciting plans in progress and we're now in the fortunate position of seeking quotations for some development work. For more details please see this page on our website: https://www.yoctoproject.org/community/yocto-project-engineering-request-for-quotation/
*YP 4.0.35 is queued for QA
*The automated regression reporting saw some issues for the M1 report so this is being worked on.
*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.
*There are pending patches to enable layer-<layername> overrides which is particularly useful for enabling layer specific QA checks. This does bring some changes of behavior for QA checks on bbappends
*Issues with pending work needed:
*usrmerge is now enabled by default for poky-altcfg, in preparation for the changes being required by systemd.
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
*The 6.1 kernel hang regression was identified and we reverted the problematic patch until the correct fix merges and filters through the stable kernel trees.
**Reports of pseudo errors on Fedora 44 beta related to openat2()
*There have been a lot of ptest issues this week, not least after issues with “No-section” tracebacks were fixed, leading to an increase in reported failures as that was masking issues. There are some fixes proposed for ptest-runner but further help is needed on the various failures.
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
*We have been approached by a potential new maintainer for the eclipse plugins. There were some questions about who was still using it and what the test matrix should look like so please let us know if you are and we can connect you.
**Meta-oe cve layer filtering under new tooling (metrics script tweak?)
*The tunctl functionality for runqemu has been dropped as the ip tool can handle everything needed.
**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/>
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: patchtest, layerindex, devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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/
*There are bugs that are currently unassigned for YP 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*Help is very much welcome in trying to resolve our autobuilder intermittent 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.
*Help us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''YP 4.3 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 4.3 M1 is released
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 4.3 M2 build date  2023/07/17
*YP 4.3 M2 Release date 2023/07/28
*YP 4.3 M3 build date  2023/08/28
*YP 4.3 M3 Release date 2023/09/08
*YP 4.3 M4 build date  2023/10/02
*YP 4.3 M4 Release date 2023/10/27
 
'''Upcoming dot releases:'''<br/>
*YP 3.1.26 is in QA
*YP 4.0.11 build date 2023/06/26
*YP 4.0.11 Release date 2023/07/07
*YP 4.2.2 build date 2023/07/10
*YP 4.2.2 Release date 2023/07/21
*YP 3.1.27 build date 2023/07/31
*YP 3.1.27 Release date 2023/08/11
*YP 4.0.12 build date 2023/08/07
*YP 4.0.12 Release date 2023/08/18
*YP 4.2.3 build date 2023/08/28
*YP 4.2.3 Release date 2023/09/08
*YP 3.1.28 build date 2023/09/18
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.13 build date 2023/09/25
*YP 4.0.13 Release date 2023/10/06
*YP 3.1.29 build date 2023/10/30
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.14 build date 2023/11/06
*YP 4.0.14 Release date 2023/11/17
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2474 (last week 2524) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2777 (last week 2797) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1152 (last week 1161)
**Total patches found: 1072 (last week 1060)
**Patches in the Pending State: 265 (23%) [last week 271 (23%)]
**Patches in the Pending State: 147 (14%) [last week 148 (14%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''YP 6.0 Milestone Dates:'''<br/>
*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:'''<br/>
*YP 5.0.17 is in review.
*YP 4.0.35 is in QA.
*YP 5.3.4
**Build Date  2026-04-20
**Release Date 2026-05-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


'''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 76: 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]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 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"