Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(212 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 31st, 2023 ==
== Yocto Project Weekly Status Oct. 28th, 2025 ==
Current Dev Position: YP 4.2 M3<br/>
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release<br/>
Next Deadline: 20th February 2023 YP 4.2 M3 Build<br/>
Next Deadline: YP 5.3 M4 Build Date 2025-11-10<br/>


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.7 and YP 4.2 M2 are in QA
*YP 5.3 M3 is in QA
*We switched to the 6.1 kernel by default for M2. Unfortunately there are a couple of intermittent issues that seem to have crept in. One is a reproducibility issue in perf, likely with some host component causing it as it only occurs on second builds. The second appears to be an intermittent networking issue accessing a python http-server for testing dnf which appeared after the kernel version change.
*YP 5.0.13 is under review for release
*We are continuing to see other intermittent failures which are limiting how quickly we can merge changes. A summary of some of the key issues was sent to the mailing list: https://lists.openembedded.org/g/openembedded-core/message/176476
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*There have been changes to the way the codeparser cache in bitbake stores data which should reduce cache size, reduce the times data needs to be written out and generally help performance.
*We have now past feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
*CVE levels in master are still high but there are patches in progress for most issues as I understand it.
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. We are evaluating the situation with 6.17, feedback on it (for/against and known issues) would be welcome.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.


'''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!
*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!
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
*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
*There are bugs identified as possible for newcomers to the project: https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs
*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.
*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.
*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 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  
*Help us resolve CVE issues: CVE metrics  
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*Ongoing project development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing We need to continue to develop this as it will allow us to potentially find ways to fund specific work items.


'''YP 4.2 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.2 M2 built and in QA
*WDD 3001 (last week 3009) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.2 M3 build date 2023/02/20
*OE-Core/Poky Patch Metrics
*YP 4.2 M3 Release date 2023/03/03
**Total patches found: 1091 (last week 1091)
*YP 4.2 M4 build date 2023/04/03
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*YP 4.2 M4 Release date 2023/04/28
*https://autobuilder.yocto.io/-release/patchmetrics/
 
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.7 built and in QA
*YP 5.0.13 is in review for release.
*YP 3.1.23 build date 2023/02/13
*YP 4.0.31 Build Date 2025-11-03
*YP 3.1.23 Release date 2023/02/24
*YP 4.0.31 Release Date 2025-11-14
*YP 4.0.8 build date 2023/02/27
*YP 5.0.14 Build Date 2025-11-17
*YP 4.0.8 Release date 2023/03/10
*YP 5.0.14 Release Date 2025-11-28
*YP 4.1.3 build date 2023/03/06
*YP 4.0.32 Build Date 2025-12-15
*YP 4.1.3 Release date 2023/03/17
*YP 4.0.32 Release Date 2025-12-24
*YP 3.1.24 build date 2023/03/20
*YP 5.0.15 Build Date 2026-01-05
*YP 3.1.24 Release date 2023/03/31
*YP 5.0.15 Release Date 2026-01-16
*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/>
*WDD 2447 (last week 2442) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1205 (last week 1190)
**Patches in the Pending State: 280 (23%) [last week 279 (23%)]
*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 61: Line 62:


== Archives ==
== Archives ==
*[[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:50, 28 October 2025

Yocto Project Weekly Status Oct. 28th, 2025

Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release
Next Deadline: YP 5.3 M4 Build Date 2025-11-10

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.3 M3 is in QA
  • YP 5.0.13 is under review for release
  • Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
  • We have now past feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
    • check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
    • Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
    • The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
    • The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
    • Help welcomed to resolve these issues!
  • Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. We are evaluating the situation with 6.17, feedback on it (for/against and known issues) would be welcome.
  • “poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
  • There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

Ways to contribute:

Tracking Metrics:

YP 5.3 Milestone Dates:

  • YP 5.3 M3 is in QA.
  • YP 5.3 M4 Build Date 2025-11-10
  • YP 5.3 M4 Release Date 2025-11-28

Upcoming dot releases:

  • YP 5.0.13 is in review for release.
  • YP 4.0.31 Build Date 2025-11-03
  • YP 4.0.31 Release Date 2025-11-14
  • YP 5.0.14 Build Date 2025-11-17
  • YP 5.0.14 Release Date 2025-11-28
  • YP 4.0.32 Build Date 2025-12-15
  • YP 4.0.32 Release Date 2025-12-24
  • YP 5.0.15 Build Date 2026-01-05
  • YP 5.0.15 Release Date 2026-01-16

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