Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(225 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 10th, 2023 ==
== Yocto Project Weekly Status Dec. 16th, 2025 ==
Current Dev Position: YP 4.2 M2<br/>
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: 23rd January 2023 YP 4.2 M2 Build<br/>
Next Deadline: YP 6.0 M1 Build Date 2026-01-05<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday January 12th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Dec. 18th at 7:30 am PST, then Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday January 10th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Dec. 18th 8 am PDT, then Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday  Dec. 18th 10am GMT and Monday Dec. 22th 9am PDT, then Monday 5th January 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.1.2 is in QA
*YP 5.3 was released, thanks to everyone who helped make it happen!
*A large number of package upgrades have merged bringing us up to date with various upstreams.
*YP 4.0.32 is in QA
*We have started moving code out of core bbclass files into the function libraries to help reduce parsing memory use, volumes of data transfer and sstate signature data sizes. Help is welcome in developing further patches to improve our function libraries.
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*The autobuilder controller has been relocated to deal with connectivity issues, we do have some issues to iron out before things are back to normal service. We were unable to upgrade the buildbot version as there were too many other moving pieces.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We are trying to upgrade uninative to include libgcc to deal with pthread_cancel failures.  Newer versions of patchelf are proving problematic and appear to be causing segfaults and we’re trying to untangle this from other issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*We have reverted the tune for qemux86-64 back to corei7-64 since we still have v2 hardware that won’t work properly with v3 under KVM and similar.
*Further bitbake-setup changes under discussion for the new development cycle:
*A uninative bug has been exposed by recent bitbake datastore improvements which could cause sstate to be missed/duplicated.
**defaulting to a common sstate directory and hashequiv server
*We merged a number of neat rust improvements which add on target cargo support and added automated QA tests for this functionality so we can ensure it continues to work and doesn’t regress. Thanks Alex Kiernan, we hope to see more series like this one!
**Allowing symlinking of local existing repos into the build instead of fetching
*CVE levels in master are becoming worrying again, help would be appreciated to address the open issues.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*The autobuilder maintenance window now occurs on Mondays.
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''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 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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 https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*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.
 
'''Tracking Metrics:'''<br/>
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
 
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.3 M4 is released.
 
'''YP 6.0 Milestone Dates:'''<br/>
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*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 4.2 Milestone Dates:'''<br/>
*YP 4.2 M2 build date 2023/01/23
*YP 4.2 M2 Release date 2023/02/03
*YP 4.2 M3 build date 2023/02/20
*YP 4.2 M3 Release date 2023/03/03
*YP 4.2 M4 build date 2023/04/03
*YP 4.2 M4 Release date 2023/04/28


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.1.2 built and in QA
*YP 4.0.32 is in QA.
*YP 4.1.2 Release date 2023/01/20
*YP 5.0.15 Build Date 2026-01-05
*YP 3.1.22 build date 2023/01/16
*YP 5.0.15 Release Date 2026-01-16
*YP 3.1.22 Release date 2023/01/27
*YP 5.3.1 Build Date 2026-01-12
*YP 4.0.7 build date 2023/01/30
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.7 Release date 2023/02/10
*YP 4.0.33 Build Date 2026-01-26
*YP 3.1.23 build date 2023/02/13
*YP 4.0.33 Release Date 2026-01-30
*YP 3.1.23 Release date 2023/02/24
*YP 5.0.16 Build Date 2026-02-09
*YP 4.0.8 build date 2023/02/27
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.8 Release date 2023/03/10
*YP 5.3.2 Build Date 2026-02-16
*YP 4.1.3 build date 2023/03/06
*YP 5.3.2 Release Date 2026-02-27
*YP 4.1.3 Release date 2023/03/17
*YP 4.0.34 Build Date 2026-02-23
*YP 3.1.24 build date 2023/03/20
*YP 4.0.34 Release Date 2026-03-06
*YP 3.1.24 Release date 2023/03/31
*YP 5.3.3 Build Date 2026-03-09
*YP 4.0.9 build date 2023/04/10
*YP 5.3.3 Release Date 2026-03-20
*YP 4.0.9 Release date 2023/04/21
*YP 5.0.17 Build Date 2026-03-16
*YP 4.1.4 build date 2023/05/01
*YP 5.0.17 Release Date 2026-03-23
*YP 4.1.4 Release date 2023/05/13
*YP 4.0.35 Build Date 2026-04-06
*YP 3.1.25 build date 2023/05/08
*YP 4.0.35 Release Date 2026-04-17
*YP 3.1.25 Release date 2023/05/19
*YP 5.3.4 Build Date 2026-04-13
*YP 4.0.10 build date 2023/05/15
*YP 5.3.4 Release Date 2026-04-24
*YP 4.0.10 Release date 2023/05/26
*YP 5.0.18 Build Date 2026-04-20
 
*YP 5.0.18 Release Date 2026-05-01
'''Tracking Metrics:'''<br/>
*YP 5.0.19 Build Date 2026-05-26
*WDD 2447 (last week 2457) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.19 Release Date 2026-06-05
*OE-Core/Poky Patch Metrics
**Total patches found: 1176 (last week 1189)
**Patches in the Pending State: 281 (24%) [last week 282 (24%)]
*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 72: Line 85:


== 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 15:51, 16 December 2025

Yocto Project Weekly Status Dec. 16th, 2025

Current Dev Position: YP 6.0 M1
Next Deadline: YP 6.0 M1 Build Date 2026-01-05

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.3 was released, thanks to everyone who helped make it happen!
  • YP 4.0.32 is in QA
  • The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
  • Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
  • We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
  • Further bitbake-setup changes under discussion for the new development cycle:
    • defaulting to a common sstate directory and hashequiv server
    • Allowing symlinking of local existing repos into the build instead of fetching
  • The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
  • We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

Ways to contribute:

Tracking Metrics:

YP 5.3 Milestone Dates:

  • YP 5.3 M4 is released.

YP 6.0 Milestone Dates:

  • YP 6.0 M1 Build Date 2026-01-05
  • YP 6.0 M1 Release Date 2026-01-16
  • 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 4.0.32 is in QA.
  • YP 5.0.15 Build Date 2026-01-05
  • YP 5.0.15 Release Date 2026-01-16
  • YP 5.3.1 Build Date 2026-01-12
  • YP 5.3.1 Release Date 2026-01-23
  • YP 4.0.33 Build Date 2026-01-26
  • YP 4.0.33 Release Date 2026-01-30
  • 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=86733"