Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(118 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 2nd, 2024 ==
== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-02<br/>
6
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday April 4th at 7:30 am 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)
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.17 has been released.
* YP 5.0.15 was released
*YP 4.3.4 is in QA and is the final planned nanbield release.
* YP 5.3.1 is under review
*YP 5.0 rc1 is now due to build when ready.
* YP 6.0 M1 is in QA
*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.
* YP 4.0.33 is queued for QA after 6.0 M1
*5.0 build status:
* YP 6.0 M2 is due next week!
**The opkg lock issue has been worked around for now in the run-postinsts script
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
**An intermittent oe-selftest failure (sstatetests hang) was tracked down to a race in tinfoil event handling.
* There are currently 6 high open bugs, which will block M2:
**The public hash equivalence server changes aren’t ready yet unfortunately
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**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.
** x86 kvm broken on Fedora 43 (#16074)
**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.
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
*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.
** Hangs of the autobuilder controller (database locking?) (#16129)
*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.
** Generation of releases.json needs updating (#16138)
*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.
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Debian 12 and Fedora 40 containers have been added to crops (Thanks Rob Wolley)
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*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
 
'''Tracking Metrics:'''<br/>
* WDD 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
 
'''YP 6.0 Milestone Dates:'''<br/>
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26


'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.17 is released.
*YP 5.3.1 is under review.
*YP 4.3.4 is in QA.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 3.1.33 build date 2024/04/15
*YP 5.0.16 Build Date 2026-02-09
*YP 3.1.33 Release date 2024/04/26
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.18 build date 2024/04/22
*YP 5.3.2 Build Date 2026-02-16
*YP 4.0.18 Release date 2024/05/03
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.19 build date 2024/06/03
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.19 Release date 2024/06/14
*YP 4.0.34 Release Date 2026-03-06
 
*YP 5.3.3 Build Date 2026-03-09
'''Tracking Metrics:'''<br/>
*YP 5.3.3 Release Date 2026-03-20
*WDD 2681 (last week 2703) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.17 Build Date 2026-03-16
*OE-Core/Poky Patch Metrics
*YP 5.0.17 Release Date 2026-03-23
**Total patches found: 1173 (last week 1156)
*YP 4.0.35 Build Date 2026-04-06
**Patches in the Pending State: 249 (21%) [last week 249 (22%)]
*YP 4.0.35 Release Date 2026-04-17
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05


'''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 79:


== 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:24, 27 January 2026

Yocto Project Weekly Status Jan. 27th, 2026

Current Dev Position: YP 6.0 M1
Next Deadline: YP 6.0 M2 Build Date 2026-02-02
6 Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.15 was released
  • YP 5.3.1 is under review
  • YP 6.0 M1 is in QA
  • YP 4.0.33 is queued for QA after 6.0 M1
  • YP 6.0 M2 is due next week!
  • Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
  • There are currently 6 high open bugs, which will block M2:
    • Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
    • x86 kvm broken on Fedora 43 (#16074)
    • AB-INT: build-sysroots: useradd command did not succeed (#16135)
    • Hangs of the autobuilder controller (database locking?) (#16129)
    • Generation of releases.json needs updating (#16138)
  • The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
  • Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.


Ways to contribute:

New to the project?

Tracking Metrics:


YP 6.0 Milestone Dates:

  • YP 6.0 M2 Build Date 2026-02-02
  • YP 6.0 M2 Release Date 2026-02-13
  • YP 6.0 M3 Build Date 2026-03-02
  • YP 6.0 M3 Release Date 2026-03-13
  • YP 6.0 M4 Build Date 2026-03-30
  • YP 6.0 M4 Release Date 2026-04-26


Upcoming dot releases:

  • YP 5.3.1 is under review.
  • YP 4.0.33 is queued for QA after 6.0 M1.
  • YP 5.0.16 Build Date 2026-02-09
  • YP 5.0.16 Release Date 2026-02-20
  • YP 5.3.2 Build Date 2026-02-16
  • YP 5.3.2 Release Date 2026-02-27
  • YP 4.0.34 Build Date 2026-02-23
  • YP 4.0.34 Release Date 2026-03-06
  • YP 5.3.3 Build Date 2026-03-09
  • YP 5.3.3 Release Date 2026-03-20
  • YP 5.0.17 Build Date 2026-03-16
  • YP 5.0.17 Release Date 2026-03-23
  • YP 4.0.35 Build Date 2026-04-06
  • YP 4.0.35 Release Date 2026-04-17
  • YP 5.3.4 Build Date 2026-04-13
  • YP 5.3.4 Release Date 2026-04-24
  • YP 5.0.18 Build Date 2026-04-20
  • YP 5.0.18 Release Date 2026-05-01
  • YP 5.0.19 Build Date 2026-05-26
  • YP 5.0.19 Release Date 2026-06-05

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