Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(321 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Apr. 12th, 2022 ==
== Yocto Project Status 21 April 2026 ==
Current Dev Position: YP 4.1 M1<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: 30th May 2022 YP 4.1 M1 build<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 Apr. 14th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Apr. 23rd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday May 3rd at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Apr. 21st 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Apr. 12th at 8 am 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)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*The next release, kirkstone will be 4.0 (previously known as 3.5) and will be bitbake 2.0 based.
*YP 5.0.17 was released
*The first release candidate build for YP 4.0 (3.5) is in QA but has at least one issue which will mean we need a second release candidate build. We will build that after the final QA report is back.
*YP 6.0 M3 was released
*YP 3.3.6, the final hardknott release will build after 4.0 rc2.
*YP 4.0.35 is in QA
*There are several issues which have arisen in the last week which mean we will need a second release candidate build:
*YP 6.0 M4 is due to build
**edgerouter didn’t boot with rc1 due to a kernel patch issue
*We continue to triage the CVEs being reported by the new tooling.
**uninative didn’t work with libstdc++ from gcc 12 so we have an upgraded version
*Various fixes have merged or are planned to merge before the M4 release build:
**there were several CVE fixes that came in (libarchive, gzip, xz)
**Various CVE issue resolutions from CVE triage
**a key intermittent autobuilder fix was identified. <br/>
**Reproducibility issues with strace/apr-util
Not all of these were release blockers but together they mean an rc2 is appropriate.
**Make race in groff
*If anyone is aware of other issues in rc1 that need to be addressed in rc2, please let us know ASAP.
**Shadow-native tallylog issue fix
*YP 4.1 planning document is available for review at: https://docs.google.com/document/d/1-g7DatSdmIETwD3xFSCxV7MbWVVkpQvQ788mIr1MPTI/edit?usp=sharing
**Upgrade of barebox to align with an LTS release
*If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
**Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
*Intermittent issues continue to be at high levels and help is very much welcome in trying to resolve them. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT We did work out the cause of the infamous tinfoil wait_event intermittent issue.
**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:'''<br/>
'''Ways to contribute:'''<br/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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=---
*There are bugs that are currently unassigned for YP 3.5. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhancements.2FBugs
*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/
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
*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.
*Help us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing


'''YP 4.0 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 4.0 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 4.0 M4 Release date 2022/04/29


'''YP 4.1 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.1 M1 build date 2022/05/30
*WDD 2790 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.1 M1 Release date 2022/06/10
*OE-Core/Poky Patch Metrics
*YP 4.1 M2 build date 2022/07/11
**Total patches found: 1078 (last week 1072)
*YP 4.1 M2 Release date 2022/07/22
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
*YP 4.1 M3 build date 2022/08/22
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
*YP 4.1 M3 Release date 2022/09/02
*YP 4.1 M4 build date 2022/10/03
*YP 4.1 M4 Release date 2022/10/28


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.3.6 build date 2022/03/28
*YP 5.0.17 was released.
*YP 3.3.6 Release date 2022/04/08
*YP 4.0.35 is in QA.
*YP 3.1.16 build date 2022/04/25
*YP 5.3.4
*YP 3.1.16 Release date 2022/05/06
**Build Date  2026-04-20  
*YP 3.4.4 build date 2022/05/02
**Release Date 2026-05-06
*YP 3.4.4 Release date 2022/05/13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.0.1 build date 2022/05/16
*YP 4.0.1 Release date 2022/05/27
*YP 3.1.17 build date 2022/06/06
*YP 3.1.17 Release date 2022/06/17
*YP 4.0.2 build date 2022/06/27
*YP 4.0.2 Release date 2022/07/08
*YP 3.1.18 build date 2022/07/18
*YP 3.1.18 Release date 2022/07/29
*YP 4.0.3 build date 2022/08/08
*YP 4.0.3 Release date 2022/08/19
*YP 3.1.19 build date 2022/08/29
*YP 3.1.19 Release date 2022/09/09
*YP 4.0.4 build date 2022/09/19
*YP 4.0.4 Release date 2022/09/30
*YP 3.1.20 build date 2022/10/10
*YP 3.1.20 Release date 2022/10/21
*YP 4.0.5 build date 2022/10/31
*YP 4.0.5 Release date 2022/11/11
 
'''Tracking Metrics:'''<br/>
*WDD 2597 (last week 2589) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
**Total patches found: 1203 (last week 1200)
**Patches in the Pending State: 343 (29%) [last week 342 (28%)]


'''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 80: 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]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2021 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"