Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(544 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 7, 2020 ==
== Yocto Project Status 14 April 2026 ==
Current Dev Position: YP 3.2 M2<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 3.2 M2 build date 2020/7/27<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 July 9th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting - Thursday Apr. 16th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday July 7th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Project Engineering Sync - Tuesday Apr. 14th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday July 14th at 8am PDT (https://zoom.us/j/990892712)
*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.2 M1 was released.
*YP 5.0.17 is due to be released
*We’ve updated to a new version of the buildtools tarball for master and dunfell
*YP 6.0 M3 is in QA
*We continue to be concerned about autobuilder stability, we’re continuing to see high numbers of intermittent failures. You can see the list of failures we’re seeing by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT  Help is urgently needed to bring these to a manageable level.
*YP 4.0.35 is queued for QA
*We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard.
*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.
*If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area.
*Issues with pending work needed:
*It is ELC this week, please stop by the booth and/or ELC #2-track-yocto-project slack channel and say hi. There are still places available on our virtual Developer Day: https://events.linuxfoundation.org/yocto-dev-day-north-america/
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
*Another way to help the project is to help us with bugs that are currently unassigned but ideally needed during 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
**Reports of pseudo errors on Fedora 44 beta related to openat2()
*We’re pleased to announce we have a new manual in the Yocto Project documentation ‘bookshelf’ which covers the project’s testing processes and infrastructure including the autobuilder and resulttool. A work-in-progress version of this can be viewed here: https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html. So far, it contains basic information in key areas, we’re happy to take feedback on areas that are missing or need more information and/or take contributions to further extend this work.
**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.


'''YP 3.2 Milestone Dates:'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.2 M2 build date 2020/7/27
*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=---
*YP 3.2 M2 Release date 2020/8/7
*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/
*YP 3.2 M3 build date 2020/8/31
*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.
*YP 3.2 M3 Release date 2020/9/11
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*YP 3.2 M4 build date 2020/10/5
*YP 3.2 M4 Release date 2020/10/30


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 3.0.4 build date 2020/8/10
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 3.0.4 release date 2020/8/21
*YP 3.1.2 build date 2020/9/14
*YP 3.1.2 release date 2020/9/25


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2485 (last week 2470) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2777 (last week 2797) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1268 (last week 1272)
**Total patches found: 1072 (last week 1060)
**Patches in the Pending State: 497 (39%) [last week 498 (39%)]
**Patches in the Pending State: 147 (14%) [last week 148 (14%)]
**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 43: 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]]
*[[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]]

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