Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(153 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 2nd, 2024 ==
== Yocto Project Status 25 August 2026 ==
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday April 4th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 27th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday April 2nd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 25th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 27th Aug. 10am GMT and Monday 31st Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.17 has been released.
*YP 6.0.3 is in QA.
*YP 4.3.4 is in QA and is the final planned nanbield release.
*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
*YP 5.0 rc1 is now due to build when ready.
*For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
*Steve is taking patches for Dunfell until around April 8 in preparation for an April 15 build. This will be the last release of dunfell.
*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
*5.0 build status:
*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
**The opkg lock issue has been worked around for now in the run-postinsts script
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**An intermittent oe-selftest failure (sstatetests hang) was tracked down to a race in tinfoil event handling.
**Matchbox-wm segfault/xserver restart
**The public hash equivalence server changes aren’t ready yet unfortunately
**aarch64/x86-64 build host contamination/reproducibility issue
**There are issues with the size of the buildhistory repository which is being split up, this needs to happen before we can build the release.
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
**A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated. This will now be the main delay on the release timeframe.
*Remaining intermittent build failures of concern:
*A new yocto-status https://lists.yoctoproject.org/g/yocto-status/topics mailing list has been created where we plan to send just the project weekly status reports and any other suitable updates on the project. This should help those who found the traffic of the other mailing lists too much.
**other qemu ‘hang’ type issues on ARM
*A yocto-patches https://lists.yoctoproject.org/g/yocto-patches/topics mailing list has been setup and patches that used to go to the yocto@ list will be migrating over to this new list, making yocto@ a bit more friendly for questions and discussions.
**sometimes yocto-check-layer is showing checksum mismatch issues
*Some other obsolete mailing lists were removed or made read-only to try and make it easier for people to find the right place to see/send things.
**intermittent ptest failures in many recipes
*Debian 12 and Fedora 40 containers have been added to crops (Thanks Rob Wolley)
*All the crops yocto-base containers now include python3-virtualenv
*The “Binary Distro” work is now well underway and there are PR Server passthrough patches ready for review. The wiki page https://wiki.yoctoproject.org/wiki/Binary_Distro_Prototype#Policies_and_Processes has had a number of policy/process proposals documented, at least as a first pass. Help is welcome to help improve these, or highlight where further documentation is needed.
*One year after the original linux.com article, an update was published: https://www.yoctoproject.org/blog/2024/03/28/maintainer-confidential-challenges-and-opportunities-one-year-on/
*There was a significant security issue with xz release tarballs. We never merged the affected version and it was never in any of our main branches but we did test it on the autobuilder and saw build failures. We continue to watch for information on any potential implications of that. We have removed the compromised tarballs from our mirrors.
*We continue to watch the NIST NVD (CVE database) situation, the recent update didn’t clarify much. Unfortunately there doesn’t appear to be a clear path forward as yet.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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/
*There are bugs that are currently unassigned for YP 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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.
 
*Help us resolve CVE issues: CVE metrics
'''New to the project?'''<br/>
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 5.0 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 5.0 M4 build date  2024/04/01
*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0 M4 Release date 2024/04/30
*OE-Core/Poky Patch Metrics
**Total patches found: 1028 (last week 1030)
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming development releases:'''<br/>
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.17 is released.
*YP 6.0.3 is in QA.
*YP 4.3.4 is in QA.
**Release Date w/c 2026-08-24
*YP 3.1.33 build date 2024/04/15
*YP 5.0.20
*YP 3.1.33 Release date 2024/04/26
**Build Date w/c 2026-08-17
*YP 4.0.18 build date 2024/04/22
**Release Date w/c 2026-08-31
*YP 4.0.18 Release date 2024/05/03
*YP 6.0.4
*YP 4.0.19 build date 2024/06/03
**Build Date w/c 2026-09-28
*YP 4.0.19 Release date 2024/06/14
**Release Date w/c 2026-10-12
*YP 5.0.21
**Build Date w/c 2026-10-05
**Release Date w/c 2026-10-19


'''Tracking Metrics:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*WDD 2681 (last week 2703) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1173 (last week 1156)
**Patches in the Pending State: 249 (21%) [last week 249 (22%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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 63: Line 68:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]

Latest revision as of 14:45, 25 August 2026

Yocto Project Status 25 August 2026

Current Dev Position: YP 6.1 M3
Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 6.0.3 is in QA.
  • YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
  • For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
  • AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
  • We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
  • There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
    • Matchbox-wm segfault/xserver restart
    • aarch64/x86-64 build host contamination/reproducibility issue

We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.

  • Remaining intermittent build failures of concern:
    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • intermittent ptest failures in many recipes

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M3:
    • Build Date: w/c 2026-08-31
    • Release Date: w/c 2026-09-14
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 6.0.3 is in QA.
    • Release Date w/c 2026-08-24
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • Release Date w/c 2026-08-31
  • YP 6.0.4
    • Build Date w/c 2026-09-28
    • Release Date w/c 2026-10-12
  • YP 5.0.21
    • Build Date w/c 2026-10-05
    • Release Date w/c 2026-10-19

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