Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
Line 1: Line 1:
== Yocto Project Weekly Status Oct. 22nd,  2024 ==
== Yocto Project Weekly Status Oct. 29th,  2024 ==
Current Dev Position: YP 5.2 M1<br/>
Current Dev Position: YP 5.2 M1<br/>
Next Deadline: YP 5.2 M1 Release date 2024-12-09<br/>
Next Deadline: YP 5.2 M1 Release date 2024-12-09<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Oct. 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Oct. 31st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Oct. 22nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync Tuesday Oct. 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester  
*Twitch -  See https://www.twitch.tv/theyoctojester  


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.1 was released - Thanks to everyone who helped contribute to 5.1!
*YP 4.0.22 was released
*YP 4.0.22 is due to release
*The new autobuilder cluster (valkyrie) is up and running and all work is being done there. The old cluster is being shut down.
*We are continuing with the autobuilder migration and the typhoon cluster is being decommissioned. All builds are now happening on valkyrie (the new cluster).
*The CDN and mirror tests are now working reliably and we are getting green builds again. Huge thanks to Michael Halstead for the work being done, mostly behind the scenes.
*There are still a lot of failures occurring on the autobuilder. Of the remaining issues, we are making progress on many but work is still ongoing.
*Progress has been made on many of the blocking intermittent issues on the new autobuilder but many rarer issues remain.
*In particular it was found the debian 11 5.10 kernel was problematic with qemu and the 6.1 kernel appears more stable for our workloads. We will switch the debian 11 workers to the 6.1 backport kernel.
*Rust tests on the MIPS architecture have been disabled as nobody is using/supporting it.
*We plan to disable the rust tests for mips and ppc, we cannot find any users of rust on these architectures.
*Toaster test suite improvements have merged but more work really needs to be done there to improve some of the test conditions.
*We have a new command line tool to help with the SWAT, thanks to Mathieu for putting that together. https://git.yoctoproject.org/swat-tools/
*The UKI (Unified Kernel Images) series finally merged with tests, which will help ensure the code keeps working in the future.
*We’re seeing a pattern of people submitting patches to master when they’ve only tested them against older releases. In several cases the issue wasn’t even present there. Please don’t do this, it wastes a lot of time. If you see the issue against an older release, please make that clear.
*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:
*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
**Autobuilder
Line 40: Line 43:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2776 (last week 2774) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2756 (last week 2776) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1078 (last week 1075)
**Total patches found: 1063 (last week 1078)
**Patches in the Pending State: 175 (16%) [last week 175 (16%)]
**Patches in the Pending State: 175 (16%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/
'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 is released.


'''YP 5.2 Milestone Dates:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
Line 60: Line 60:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.22 is in review.
*YP 4.0.22 was released.
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Release Date 2024-11-22
*YP 5.0.5 Release Date 2024-11-22

Latest revision as of 14:41, 29 October 2024

Yocto Project Weekly Status Oct. 29th, 2024

Current Dev Position: YP 5.2 M1
Next Deadline: YP 5.2 M1 Release date 2024-12-09

Next Team Meetings:

Key Status/Updates:

  • YP 4.0.22 was released
  • The new autobuilder cluster (valkyrie) is up and running and all work is being done there. The old cluster is being shut down.
  • The CDN and mirror tests are now working reliably and we are getting green builds again. Huge thanks to Michael Halstead for the work being done, mostly behind the scenes.
  • Progress has been made on many of the blocking intermittent issues on the new autobuilder but many rarer issues remain.
  • Rust tests on the MIPS architecture have been disabled as nobody is using/supporting it.
  • Toaster test suite improvements have merged but more work really needs to be done there to improve some of the test conditions.
  • We have a new command line tool to help with the SWAT, thanks to Mathieu for putting that together. https://git.yoctoproject.org/swat-tools/
  • The UKI (Unified Kernel Images) series finally merged with tests, which will help ensure the code keeps working in the future.
  • We’re seeing a pattern of people submitting patches to master when they’ve only tested them against older releases. In several cases the issue wasn’t even present there. Please don’t do this, it wastes a lot of time. If you see the issue against an older release, please make that clear.
  • 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:

  • 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://wiki.yoctoproject.org/wiki/Newcomers
  • 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
  • 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.

Tracking Metrics:

YP 5.2 Milestone Dates:

  • YP 5.2 M1 Build Date 2024-12-09
  • YP 5.2 M1 Release Date 2024-12-20
  • YP 5.2 M2 Build Date 2025-01-20
  • YP 5.2 M2 Release Date 2025-01-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:

  • YP 4.0.22 was released.
  • YP 5.0.5 Build Date 2024-11-11
  • YP 5.0.5 Release Date 2024-11-22
  • YP 4.0.23 Build Date 2024-11-18
  • YP 4.0.23 Release Date 2024-11-29
  • YP 5.1.1 Build Date 2024-12-02
  • YP 5.1.1 Release Date 2024-12-13
  • YP 5.0.6 Build Date 2024-12-16
  • YP 5.0.6 Release Date 2024-12-27
  • YP 4.0.24 Build Date 2025-01-06
  • YP 4.0.24 Release Date 2025-01-17
  • YP 5.1.2 Build Date 2025-01-13
  • YP 5.1.2 Release Date 2025-01-24
  • YP 5.0.7 Build Date 2025-01-27
  • YP 5.0.7 Release Date 2025-02-07
  • YP 4.0.25 Build Date 2025-02-17
  • YP 4.0.25 Release Date 2025-02-28
  • YP 5.1.3 Build Date 2025-02-24
  • YP 5.1.3 Release Date 2025-03-07
  • YP 5.0.8 Build Date 2025-03-10
  • YP 5.0.8 Release Date 2025-03-21
  • YP 5.1.4 Build Date 2025-03-24
  • YP 5.1.4 Release Date 2025-04-04
  • YP 4.0.26 Build Date 2025-04-07
  • 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:
https://wiki.yoctoproject.org/wiki/TSC

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86485"