Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(653 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status March, 19, 2019 ==
== Yocto Project Status 21 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. 23rd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 21st 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 23rd 10am GMT and Monday Apr. 27th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*M3 has not built yet however most major pieces are in place, including now, agreement on the new QA process. The delay is partly due to RP travel with others able to cover being unavailable for other reasons, combined with infrastructure issues.
*YP 5.0.17 was released
*The remaining questions for M3 are:
*YP 6.0 M3 was released
**Public documentation of the new QA process
*YP 4.0.35 is in QA
**Upgrade for uninative for glibc 2.29
*YP 6.0 M4 is due to build
**Mesa upgrade? (unlikely given failures in testing)
*We continue to triage the CVEs being reported by the new tooling.
*The Yocto Project has updated to its new governance model which includes establishing a Technical Steering Committee (TSC) for Yocto Project. This is designed to complement  and work alongside the OpenEmbedded TSC. Three members of the YP TSC are selected by the Yocto Project governing board and those people are Ross Burton, Khem Raj and Richard Purdie. The remaining two seats will be elected by OpenEmbedded. It is intended the TSC will take over the release process, SWAT team, bug triage and feature planning/development for 2.8.
*Various fixes have merged or are planned to merge before the M4 release build:
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.
**Various CVE issue resolutions from CVE triage
*There is discussion on the openembedded-architecture list about changes to the stable branch patch criteria to bring us more into line with current industry best practices and thinking.
**Reproducibility issues with strace/apr-util
**Make race in groff
**Shadow-native tallylog issue fix
**Upgrade of barebox to align with an LTS release
**Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
**Sbom-cve-check upgrade (along with dependencies)
*Issues still pending:
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
**Intermittent wic failures on the autobuilder
*At this point we will likely run the release build as the remaining issues aren’t critical to end users and we have no clear timeframe for resolution of them
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.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The final whinlatter build is happening this week.


'''Planned Releases for YP 2.7:'''<br/>
'''Ways to contribute:'''<br/>
*YP 2.7 M3 Cutoff was 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 was 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 M3 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 2432 (last week 2439) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2790 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1526 (last week 1523)
**Total patches found: 1078 (last week 1072)
**Patches in the Pending State: 656 (43%) [last week 657 (43%)]
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Key Status Links for YP:'''<br/>
'''Upcoming dot releases:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status<br/>
*YP 5.0.17 was released.
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule<br/>
*YP 4.0.35 is in QA.
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features<br/>
*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]]

Latest revision as of 14:47, 21 April 2026

Yocto Project Status 21 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 was released
  • YP 6.0 M3 was released
  • YP 4.0.35 is in QA
  • YP 6.0 M4 is due to build
  • We continue to triage the CVEs being reported by the new tooling.
  • Various fixes have merged or are planned to merge before the M4 release build:
    • Various CVE issue resolutions from CVE triage
    • Reproducibility issues with strace/apr-util
    • Make race in groff
    • Shadow-native tallylog issue fix
    • Upgrade of barebox to align with an LTS release
    • Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
    • Sbom-cve-check upgrade (along with dependencies)
  • Issues still pending:
    • 32bit x86 kvm seemingly broken with certain CPU features (#16074)
    • Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
    • Intermittent wic failures on the autobuilder
  • At this point we will likely run the release build as the remaining issues aren’t critical to end users and we have no clear timeframe for resolution of them

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.

  • We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
  • The final whinlatter build is happening this week.

Ways to contribute:

New to the project?

Tracking Metrics:

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