Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(642 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 16, 2019 ==
== Yocto Project Status 21 April 2026 ==
Current Dev Position: YP 2.7 M4 (2.7 rc2 is in QA)<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 2.7 Release Target April 26, 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: Chen
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*SWAT team rotation: Chen -> Armin on Apr. 19, 2019
*SWAT team rotation: Armin -> Anuj on Apr. 26, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
'''Next Team Meetings:'''<br/>
*YP 2.8 Planning meeting Tuesday April 16nd at 8am PDT (https://zoom.us/j/990892712)
*Bug Triage meeting Thursday April 18th at 7:30am PDT (https://zoom.us/j/454367603)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*Stephen is unavailable at the moment, please refer any queries to Richard
*YP 5.0.17 was released
*YP 2.6.2 was rebuilt as rc4 to include the boost upgrade revert and is due to be released today. The YP 2.6.2 rc3/4 report is summarized at https://lists.yoctoproject.org/pipermail/yocto/2019-April/044827.html and the results are at https://autobuilder.yocto.io/pub/releases/yocto-2.6.2.rc4/testresults/.
*YP 6.0 M3 was released
*YP 2.5.3 is currently going through the QA process.
*YP 4.0.35 is in QA
*We’re sad to announce that we will be removing eclipse plugin builds from the autobuilder and will not be including the plugin in any future project releases. This is due to a lack of anyone able to help work on the plugin development, bug fixing or release.
*YP 6.0 M4 is due to build
*The key fixes mentioned in last week’s status have been merged into 2.7.
*We continue to triage the CVEs being reported by the new tooling.
*A key bug in pseudo was identified which may be the root cause of the long standing glibc-locale uid “host contamination” issue. Many thanks to Peter and Otavio for the help in debugging that. A separate fix should also ensure pseudo works with newer distro coreutils and glibc versions.
*Various fixes have merged or are planned to merge before the M4 release build:
*YP 2.7 rc2 (warrior) was built successfully and is currently going through the QA process after 2.5.3 is done.
**Various CVE issue resolutions from CVE triage
*The ptest results in 2.7 are much more stable than ever before with results being consistent from build to build. At the start of 2.8 we can make some further improvements so we take advantage of this and build upon it to reduce regressions in the system.
**Reproducibility issues with strace/apr-util
*In an effort to keep the patch queue under control, patches are merging to master.
**Make race in groff
*The list of issues from last week of worrying things we lack resources to improve upon remains:
**Shadow-native tallylog issue fix
**Intermittent autobuilder failures (fork running out of resources - which resources?, oe-selftest intermittent issues, gpg signing resource problems, occasional PR server failure and more)
**Upgrade of barebox to align with an LTS release
**Build-appliance testing issues (show up on each QA report across multiple releases)
**Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
**40% valgrind ptest failures
**Sbom-cve-check upgrade (along with dependencies)
**Known bitbake memory resident bugs
*Issues still pending:
**Other ptest failures
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
*The 2.8 planning discussions are starting and there is a google doc summarising the discussions so far: https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
*If people are planning to work on specific things in 2.8 please let us know so we can incorporate this into our plans. If you’re interested in working on anything in the document, please also let us know or talk with us in one of the planning meetings.
**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 M4 Cutoff was Apr. 1, 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 M4 Release Target is Apr. 26, 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/
*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


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.5.3 (Sumo) is in QA.
*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/>
'''Tracking Metrics:'''<br/>
*WDD 2523  (last week 2442) (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: 1553 (last week 1553)
**Total patches found: 1078 (last week 1072)
**Patches in the Pending State: 654 (42%) [last week 655 (42%)]
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming dot releases:'''<br/>
*YP 5.0.17 was released.
*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


'''Key Status Links for YP:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features<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"