Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(274 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status December 20th, 2022 ==
== Yocto Project Status 25 August 2026 ==
Current Dev Position: YP 4.2 M2<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: 23th January 2023 YP 4.2 M2 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 December 22nd 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 December 20th 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.2 M1 and YP 4.0.6 passed QA and are due for release.
*YP 6.0.3 is in QA.
*Builds on the autobuilder are problematic at present due to connection losses with the controller machine. We understand the cause and will be migrating the controller to a new server/location to address this.
*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
*That, combined with OOM issues from recent bitbake cache changes meant patches are merging more slowly this week.
*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!
*There are a number of bitbake patches pending which are a bit more invasive than usual. These are aiming to address:
*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.
**memory issues seen with the recent cache changes and bitbake -S
*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.
**UI hangs where the bitbake server has crashed/hung or otherwise failed
*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:
**issues where bitbake may have removed another server instances bitbake.sock network socket file
**Matchbox-wm segfault/xserver restart
**console interaction issues where bitbake may not respond to Ctrl+C
**aarch64/x86-64 build host contamination/reproducibility issue
**event handler race issues around datastore accesses
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.
*The OE TSC decided in favour of adding export flag expansion despite the performance impact so that patch will be queued.
*Remaining intermittent build failures of concern:
*CVE levels in master are concerning again
**other qemu ‘hang’ type issues on ARM
*With some debugging, the bitbake.sock disappearance was potentially identified and also issues with OOM process killing locking up bitbake’s server and UI were studied.
**sometimes yocto-check-layer is showing checksum mismatch issues
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
**intermittent ptest failures in many recipes
*There will be no status report next week, the next will be 3rd January 2023.


'''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: patchtest, layerindex, 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 4.2 See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*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 https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 4.2 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.2 M1 is ready for released
*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.2 M2 build date 2023/01/23
*OE-Core/Poky Patch Metrics
*YP 4.2 M2 Release date 2023/02/03
**Total patches found: 1028 (last week 1030)
*YP 4.2 M3 build date 2023/02/20
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
*YP 4.2 M3 Release date 2023/03/03
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
*YP 4.2 M4 build date 2023/04/03
 
*YP 4.2 M4 Release date 2023/04/28
'''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.6 is out of QA
*YP 6.0.3 is in QA.
*YP 4.1.2 build date 2023/01/09
**Release Date w/c 2026-08-24
*YP 4.1.2 Release date 2023/01/20
*YP 5.0.20
*YP 3.1.22 build date 2023/01/16
**Build Date w/c 2026-08-17
*YP 3.1.22 Release date 2023/01/27
**Release Date w/c 2026-08-31
*YP 4.0.7 build date 2023/01/30
*YP 6.0.4
*YP 4.0.7 Release date 2023/02/10
**Build Date w/c 2026-09-28
*YP 3.1.23 build date 2023/02/13
**Release Date w/c 2026-10-12
*YP 3.1.23 Release date 2023/02/24
*YP 5.0.21
*YP 4.0.8 build date 2023/02/27
**Build Date w/c 2026-10-05
*YP 4.0.8 Release date 2023/03/10
**Release Date w/c 2026-10-19
*YP 4.1.3 build date 2023/03/06
*YP 4.1.3 Release date 2023/03/17
*YP 3.1.24 build date 2023/03/20
*YP 3.1.24 Release date 2023/03/31
*YP 4.0.9 build date 2023/04/10
*YP 4.0.9 Release date 2023/04/21
*YP 4.1.4 build date 2023/05/01
*YP 4.1.4 Release date 2023/05/13
*YP 3.1.25 build date 2023/05/08
*YP 3.1.25 Release date 2023/05/19
*YP 4.0.10 build date 2023/05/15
*YP 4.0.10 Release date 2023/05/26


'''Tracking Metrics:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*WDD 2462 (last week 2437) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1161 (last week 1162)
**Patches in the Pending State: 282 (24%) [last week 285 (25%)]
*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 77: Line 68:


== 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]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 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"