Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(586 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status September 3, 2019 ==
== Yocto Project Weekly Status Oct. 28th, 2025 ==
Current Dev Position: YP 2.8 M4 Feature Freeze<br/>
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release<br/>
Next Deadline: YP 3.0 Final Release 25th Oct<br/>
Next Deadline: YP 5.3 M4 Build Date 2025-11-10<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
*SWAT lead is currently: Armin
*Bug Triage meeting - Thursday Oct. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*SWAT team rotation: Armin -> Paul on Sept. 6, 2019
*Weekly Project Engineering Sync - Tuesday Oct. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*SWAT team rotation: Paul -> Ross on Sept. 13, 2019
*Yocto Project Patch Review - Thursday Oct. 30th 10am GMT and Monday Nov. 3rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)
*://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday August 5th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Sept. 3rd at 8am PDT (https://zoom.us/j/990892712)
*Twitch - Next event is Sept. 10th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We’re now in feature freeze for 3.0 and working on bug fixing for final release
*YP 5.3 M3 is in QA
*Several key 3.0 changes have now merged:
*YP 5.0.13 is under review for release
**5.2 linux-libc-kernel-headers
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
**5.2 kernel recipes
*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:
**Removal of LSB and poky-lsb and replacement with alt config testing
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Patches have significantly reduced the dependency on python2
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**Reproducible builds are now being tested for core-image-minimal
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
*There are the following changes still under discussion/testing:
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Systemd vs. sysvinit defaults (maybe for the poky alternative configuration tests)
**Help welcomed to resolve these issues!
**Making 5.2 the default kernel for qemu (has regressions, see below)
*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.
**Hashserv performance issue resolution
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
**Final configuration of hash equivalency
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
**toolchain testsuite patch series
 
*The sstate hash equivalency continues to have challenges:
'''Ways to contribute:'''<br/>
**we need to rework the client/server communication to scale to the autobuilder
*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 some bugs in the code the autobuilder continues to expose
*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
**we have cases where its not 100% clear what the correct behaviour should be
*There are bugs identified as possible for newcomers to the project: https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
**test cases are proving to be problematic to write in a maintainable way
*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
*Patch merging is roughly up to date again
*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 have several significant problematic bugs that are being worked on:
*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.
**5.2 stap build issue on qemuarm
*Help us resolve CVE issues: CVE metrics
**5.2 kprobes error message (qemuarm64, qemumips64)
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
**qemumips machine hang
*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.
8If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+Stephen.


'''Planned Releases for YP 3.0 {2.8}:'''<br/>
'''Tracking Metrics:'''<br/>
*M3 Release 6th Sept
*WDD 3001 (last week 3009) (https://wiki.yoctoproject.org/charts/combo.html)
*M4 Cutoff 30th Sept - this will be YP 3.0.
*OE-Core/Poky Patch Metrics
*YP 3.0 {2.8 (M4)} Final Release 25th Oct
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/


'''Planned upcoming dot releases:'''<br/>
'''YP 5.3 Milestone Dates:'''<br/>
*YP 2.7.2 (Warrior) is planned for after YP 3.0 release.
*YP 5.3 M3 is in QA.
*YP 2.6.4 (Thud) is planned for after YP 2.7.2  release.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2413 (last week 2485) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.13 is in review for release.
*Poky Patch Metrics 
*YP 4.0.31 Build Date 2025-11-03
**Total patches found: 1470 (last week 1474)
*YP 4.0.31 Release Date 2025-11-14
**Patches in the Pending State: 611 (42%) [last week 613 (41%)]
*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


'''Key Status Links for YP:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features<br/>


== Archives ==
== Archives ==
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2019 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"