Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(654 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status March, 12, 2019 ==
== Yocto Project Status 14 April 2026 ==
Current Dev Position: YP 2.7 M3 <br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019<br/>
Next Deadline: YP 6.0 M4 Build Date 2026-04-20<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday Apr. 16th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 14th 8am 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)


*SWAT lead is currently: Anuj
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*SWAT team rotation: Anuj -> Armin on Mar. 15, 2019
*SWAT team rotation: Armin -> Paul on Mar. 23, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.7 M2 rc2 was released on May 5, 2019.
*YP 5.0.17 is due to be released
*We believe we now have all the key components for 2.7M3 in master-next but have not completed a successful test run with this. In addition to the list last week, this means M3 will include:
*YP 6.0 M3 is in QA
**5.0 kernel
*YP 4.0.35 is queued for QA
**qemuarm transition to armv7
*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.
**Busybox full replacement utils
*Issues with pending work needed:
*Some invalid source revisions tested in master-next have broken the autobuilder causing build hangs and failures. With travel and other distractions, nobody is available to dive in and debug this immediately so it will block M3.
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
*We also want to complete the transition to the new QA process and test this for M3. Aproov is going to send out details of this imminently, we believe the main code work is complete and its process/documentation that remains. We will block on this as we want to use the new QA process for M3 and the final 2.7 release.
**Reports of pseudo errors on Fedora 44 beta related to openat2()
*YP 2.5.3 continues to be blocked on autobuilder-helper changes for the stable branches and the resulttool changes in master to move to the new QA process.
**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.


'''Planned Releases for YP 2.7:'''<br/>
'''Ways to contribute:'''<br/>
*YP 2.7 M3 Cutoff is Feb. 25, 2019
*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 2.7 M3 Release Target is Mar. 8, 2019
*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 2.7 M4 Cutoff is Apr. 1, 2019
*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 2.7 M4 Release Target is Apr. 26, 2019
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2439 (last week 2436) (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: 1523 (last week 1502)
**Total patches found: 1072 (last week 1060)
**Patches in the Pending State: 657 (43%) [last week 658 (44%)]
**Patches in the Pending State: 147 (14%) [last week 148 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Key Status Links for YP:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status<br/>
*YP 6.0 M3 in QA.
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule<br/>
*YP 6.0 M4 Build Date 2026-04-13
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features<br/>
*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/>
https://wiki.yoctoproject.org/wiki/TSC<br/>


== 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]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2019 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"