Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(643 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 9, 2019 ==
== Yocto Project Status 21 April 2026 ==
Current Dev Position: YP 2.7 M4 (New feature Freeze has begun.)<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019 and it should release today<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: Amanda
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*SWAT team rotation: Amanda -> Chen on Apr. 12, 2019
*SWAT team rotation: Chen -> Armin on Apr. 19, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
'''Next Team Meetings:'''<br/>
*YP 2.8 Planning meeting Tuesday April 2nd at 8am PDT (https://zoom.us/j/990892712)
*Bug Triage meeting Thursday April 4th at 7:30am PDT (https://zoom.us/j/454367603)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.7 M3 rc1 will be released today. The YP 2.7 M3 rc1 report is summarized at https://lists.yoctoproject.org/pipermail/yocto/2019-April/044667.html and the results are at https://autobuilder.yocto.io/pub/releases/yocto-2.7_M3.rc1/testresults/.
*YP 5.0.17 was released
*YP 2.5.3 and YP 2.6.2 stable releases were built and have been submitted to QA
*YP 6.0 M3 was released
*YP 2.6.2 is currently going through the QA process with YP 2.5.3 queued behind it.
*YP 4.0.35 is in QA
*Process issues in the way ptest was being processed by QA have been discovered which mean the previous ptest results are not comparable with the new QA process. For consistency going forward we will be using the new QA process as the definitive results and will be comparing for regressions based upon these.
*YP 6.0 M4 is due to build
*The “warrior” branches for 2.7 have been created and the metadata updated, patches are being slowed in line with release stablisation with increasingly critical fixes only.
*We continue to triage the CVEs being reported by the new tooling.
*The remaining things which are planned for YP 2.7 M4 before we have the final 2.7 rc1 build are:
*Various fixes have merged or are planned to merge before the M4 release build:
**Upgrading -tiny to the 5.0 linux-yocto kernel (currently 4.18)
**Various CVE issue resolutions from CVE triage
**Removal of the 4.18 kernel
**Reproducibility issues with strace/apr-util
**Fixing the python3 ptest timeout and result status issues
**Make race in groff
**Fixing some of the util-linux ptest failures
**Shadow-native tallylog issue fix
**Potentially integrating a key and long time puzzling pseudo issue
**Upgrade of barebox to align with an LTS release
**Integrating qemumips shutdown issues identified in the kernel
**Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
**Continue to investigate python3 testsuite hang on 5.0+ kernels (trying to get help upstream)
**Sbom-cve-check upgrade (along with dependencies)
*Worrying things which we don’t have good plans for currently (mainly lack of people to help with):
*Issues still pending:
**Intermittent autobuilder failures (fork running out of resources - which resources?, oe-selftest intermittent issues, gpg signing resource problems, occasional PR server failure and more)
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Build-appliance testing issues (show up on each QA report across multiple releases)
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
**40% valgrind ptest failures
**Intermittent wic failures on the autobuilder
**Known bitbake memory resident bugs
*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
**Other ptest failures
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 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/
*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.
*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.
*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
*YP 2.6.2 (Thud) is in QA.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2442 (last week 2418) (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: 1542 (last week 1538)
**Total patches found: 1078 (last week 1072)
**Patches in the Pending State: 654 (42%) [last week 656 (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"