Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(42 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Oct. 15th, 2024 ==
== Yocto Project Weekly Status July 1st, 2025 ==
Current Dev Position: YP 5.1 release pending review<br/>
Current Dev Position: YP 5.3 M2<br/>
Next Deadline: YP 5.1 M4 Release date 2024-10-25<br/>
Next Deadline: YP 5.3 M2 Build date 2025-07-21<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Oct. 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday July 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Oct. 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday July 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday July 3rd 10am GMT and Monday July 7th 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 5.0.4 was released
*YP 5.3 M1 is due to be released. One issue was found which needs to be fixed during M2: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
*YP 4.0.22 is in QA
**Help in debugging and fixing this would be very welcome.
*YP 5.1 rc1 (final release) has release notes and is pending TSC review
*YP 4.0.28 is in QA.
*We are continuing with the autobuilder migration and the typhoon cluster is being decommissioned.
*Patches continue to merge into master for upgrades and fixes.
*Unfortunately there are a large number of failures occurring on the autobuilder. These can be seen in this thread where there are 11 issues detailed, only two of which are currently resolved: https://lists.openembedded.org/g/openembedded-core/topic/108984574#msg205803
*There were git tag improvements meaning we can now start adding these to SRC_URIs in all cases as shallow clone tarballs now account for them.
*A brief one line summary of the remaining 9 issues:
*The clang build time and size increases continue to cause significant concern.
**A problem scaling writes to hashequiv which causes timeouts
*Patches to improve gomod support in devtool merged.
**A mips issue where rust selftests fail (who can help maintain mips and ppc?)
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
**zlib reproducibility problem
*OE_SHARED_UMASK was added to control the umask used for files created in the shared DL_DIR and SSTATE_DIR directories.
**Debian11 tap device problems
*For M2, the following changes have been mentioned as possibilities:
**Fedora41 selftest bitbake timeout issues
**bitbake-setup
**CDN mirroring issues due to migration (Michael working on it)
**wic split from OE-Core
**Sources mirroring issues due to migration (Michael working on it)
**RISC-V tune changes (part 2)
**CVE database corruption issue
**switch classextend to use [filter] support from bitbake
**Toaster testsuite problems
*For 5.2 it would be helpful to have rough development plans for areas of the project if anyone is able to help document a rough roadmap/plan for them. The following areas are known to be being or need working on:
**Autobuilder
**Binary Distro
**Bitbake config fragments
**Bitbake setup process/tooling
**GUI screen shot QA test
**IDE Plugin development
**Layer Index
**Patchtest
**Security Tooling
**Swatbot
**Toaster
*If there are other areas we should have plans for, please let us know.


'''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: 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 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 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://wiki.yoctoproject.org/wiki/Newcomers
*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.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_Unassigned_Enhancements/Bugs
*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.
*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/>
'''Tracking Metrics:'''<br/>
*WDD 2754 (last week 2744) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2770 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1072 (last week 1067)
**Total patches found: 1091 (last week 1093)
**Patches in the Pending State: 175 (16%) [last week 176 (16%)]
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.1  is in TSC review.
*YP 5.3 M1 is ready for release.
 
*YP 5.3 M2 Build Date 2025-07-21
'''YP 5.2 Milestone Dates:'''<br/>
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.2 M1 Build Date 2024-12-09
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.2 M1 Release Date 2024-12-20
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.2 M2 Build Date 2025-01-20
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.2 M2 Release Date 2025-01-31
*YP 5.3 M4 Release Date 2025-10-31
*YP 5.2 M3 Build Date 2025-03-03
*YP 5.2 M3 Release Date 2025-03-14
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.4 was released.
*YP 4.0.28 is in QA.
*YP 4.0.22 is in QA.
*YP 5.2.2 Build Date 2025-07-07
*YP 5.0.5 Build Date 2024-11-11
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.5 Release Date 2024-11-22
*YP 5.0.11 Build Date 2025-07-14
*YP 4.0.23 Build Date 2024-11-18
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.23 Release Date 2024-11-29
*YP 4.0.29 Build Date 2025-08-11
*YP 5.1.1 Build Date 2024-12-02
*YP 4.0.29 Release Date 2025-08-25
*YP 5.1.1 Release Date 2024-12-13
*YP 5.2.3 Build Date 2025-08-18
*YP 5.0.6 Build Date 2024-12-16
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.6 Release Date 2024-12-27
*YP 5.0.12 Build Date 2025-08-25
*YP 4.0.24 Build Date 2025-01-06
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.24 Release Date 2025-01-17
*YP 4.0.30 Build Date 2025-09-22
*YP 5.1.2 Build Date 2025-01-13
*YP 4.0.30 Release Date 2025-10-03
*YP 5.1.2 Release Date 2025-01-24
*YP 5.2.4 Build Date 2025-09-29
*YP 5.0.7 Build Date 2025-01-27
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.7 Release Date 2025-02-07
*YP 5.0.13 Build Date 2025-10-13
*YP 4.0.25 Build Date 2025-02-17
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.25 Release Date 2025-02-28
*YP 4.0.31 Build Date 2025-11-03
*YP 5.1.3 Build Date 2025-02-24
*YP 4.031 Release Date 2025-11-14
*YP 5.1.3 Release Date 2025-03-07
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.8 Build Date 2025-03-10
*YP 5.0.14 Release Date 2025-11-28
*YP 5.0.8 Release Date 2025-03-21
*YP 4.0.32 Build Date 2025-12-15
*YP 5.1.4 Build Date 2025-03-24
*YP 4.0.32 Release Date 2025-12-24
*YP 5.1.4 Release Date 2025-04-04
*YP 5.0.15 Build Date 2026-01-05
*YP 4.0.26 Build Date 2025-04-07
*YP 5.0.15 Release Date 2026-01-16
*YP 4.0.26 Release Date 2025-04-18
*YP 5.0.9 Build Date 2025-04-21
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.0.10 Build Date 2025-06-02
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11


'''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 108: Line 84:


== Archives ==
== Archives ==
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]

Revision as of 14:41, 1 July 2025

Yocto Project Weekly Status July 1st, 2025

Current Dev Position: YP 5.3 M2
Next Deadline: YP 5.3 M2 Build date 2025-07-21

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.3 M1 is due to be released. One issue was found which needs to be fixed during M2: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
    • Help in debugging and fixing this would be very welcome.
  • YP 4.0.28 is in QA.
  • Patches continue to merge into master for upgrades and fixes.
  • There were git tag improvements meaning we can now start adding these to SRC_URIs in all cases as shallow clone tarballs now account for them.
  • The clang build time and size increases continue to cause significant concern.
  • Patches to improve gomod support in devtool merged.
  • The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
  • OE_SHARED_UMASK was added to control the umask used for files created in the shared DL_DIR and SSTATE_DIR directories.
  • For M2, the following changes have been mentioned as possibilities:
    • bitbake-setup
    • wic split from OE-Core
    • RISC-V tune changes (part 2)
    • switch classextend to use [filter] support from bitbake

Ways to contribute:

Tracking Metrics:

YP 5.3 Milestone Dates:

  • YP 5.3 M1 is ready for release.
  • YP 5.3 M2 Build Date 2025-07-21
  • YP 5.3 M2 Release Date 2025-08-01
  • YP 5.3 M3 Build Date 2025-09-01
  • YP 5.3 M3 Release Date 2025-09-12
  • YP 5.3 M4 Build Date 2025-10-06
  • YP 5.3 M4 Release Date 2025-10-31

Upcoming dot releases:

  • YP 4.0.28 is in QA.
  • YP 5.2.2 Build Date 2025-07-07
  • YP 5.2.2 Release Date 2025-07-18
  • YP 5.0.11 Build Date 2025-07-14
  • YP 5.0.11 Release Date 2025-07-25
  • YP 4.0.29 Build Date 2025-08-11
  • YP 4.0.29 Release Date 2025-08-25
  • YP 5.2.3 Build Date 2025-08-18
  • YP 5.2.3 Release Date 2025-08-29
  • YP 5.0.12 Build Date 2025-08-25
  • YP 5.0.12 Release Date 2025-09-05
  • YP 4.0.30 Build Date 2025-09-22
  • YP 4.0.30 Release Date 2025-10-03
  • YP 5.2.4 Build Date 2025-09-29
  • YP 5.2.4 Release Date 2025-10-10
  • YP 5.0.13 Build Date 2025-10-13
  • YP 5.0.13 Release Date 2025-10-24
  • YP 4.0.31 Build Date 2025-11-03
  • YP 4.031 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=86650"