Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(548 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status February 18, 2020 ==
== Yocto Project Weekly Status Nov. 4th, 2025 ==
Current Dev Position: YP 3.1 M3  - At Feature Freeze <br/>
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release<br/>
Next Deadline: YP 3.1 M3 build date 2/24/2020<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 Feb. 27th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting - Thursday Nov. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Mar. 3rd at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Project Engineering Sync - Tuesday Nov. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Feb. 25th at 8am PDT (https://zoom.us/j/990892712)
*Yocto Project Patch Review - Thursday Nov. 6th 10am GMT and Monday Nov. 10th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  
*Twitch - See http://www.twitch.tv/letoatreidesthe2nd
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*The project recently updated its git hosting infrastructure and there were some issues encountered with the cgit http/https repository sharing. Those issues should now be resolved, apologies if they caused issues for anyone. The git:// protocol sharing was unaffected.
*YP 5.0.13 was released
*YP 3.0.2 rc2 is in QA with the report due soon.
*YP 5.3 M3 is due to be released
*We continue to see a small number of reproducibility issues with master which need resolving for green builds (in particular gstreamer and perl).
*YP 4.0.31 is in QA
*A significant memory usage issue was identified during bitbake parsing where memory usage would grow in each parser thread linearly per number of recipes parsed. This would therefore particularly affect large numbers of layers, multilibs and multiconfig. The fix has merged into bitbake along with the corresponding zeus and warrior branches. For one test case it reduced peak memory usage during parsing for 5 multiconfigs from 20GB to 2GB.
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*Warrior patches for 2.7.3 are out for review.
*We plan to merge the documentation changes then stop updating the poky repository master branch.
*With the git infrastructure issue updated, we now have centos8 workers added to the autobuilder.
*We are now past the feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter.  Known issues:
*We are making various queued changes to the autobuilder configuration to fix bugs, improve efficiency and test coverage but this may result in some test result instability as we test and resolve 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.
*We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
*The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.
**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. The 6.17 kernel has run into issues we don’t have availability/time to resolve unfortunately so we will have to release with 6.16.
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
 
'''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!
*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 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.
*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
*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.


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.1 M3 build date 2/24/2020
*WDD 3103 (last week 3001) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.1 M3 release date 3/6/2020
*OE-Core/Poky Patch Metrics
*YP 3.1 M4 build date  3/30/2020
**Total patches found: 1098 (last week 1091)
*YP 3.1 M4 release date  4/24/2020
**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.3 built and in QA
*YP 5.3 M3 is in review for release.
*YP 2.7.3 release date 2/21/2020
*YP 5.3 M4 Build Date 2025-11-10
*YP 3.0.2 release soon
*YP 5.3 M4 Release Date 2025-11-28
*YP 3.0.3 build date  5/4/2020
*YP 3.0.3 release date 5/15/2020
*YP 2.7.4 build date  5/18/2020
*YP 2.7.4 release date 5/29/2020


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2665 (last week 2710) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.13 was released.
*Poky Patch Metrics 
*YP 4.0.31 is in QA.
**Total patches found: 1356 (last week 1360)
*YP 5.0.14 Build Date 2025-11-17
**Patches in the Pending State: 543 (40%) [last week 546 (40%)]
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 45: Line 63:


== 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]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]

Latest revision as of 15:52, 4 November 2025

Yocto Project Weekly Status Nov. 4th, 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.0.13 was released
  • YP 5.3 M3 is due to be released
  • YP 4.0.31 is in QA
  • Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
  • We plan to merge the documentation changes then stop updating the poky repository master branch.
  • We are now past the 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. The 6.17 kernel has run into issues we don’t have availability/time to resolve unfortunately so we will have to release with 6.16.
  • YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
  • 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 review for release.
  • 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 was released.
  • YP 4.0.31 is in QA.
  • 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=86705"