Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
(23 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status March 5th, 2024 ==
== Yocto Project Weekly Status June 18th, 2024 ==
Current Dev Position: YP 5.0 M3 - Feature Freeze <br/>
Current Dev Position: YP 5.1 M2 <br/>
Next Deadline: 19th February 2024 YP 5.0 M3 build<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday March 7th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday June 13th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday March 5th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday June 11th at 8 am PDT (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/>
*We are now at feature freeze for 5.0, preparing to build M3
*YP 4.0.19 is ready for release.
*YP 4.3.3 was released
*YP 5.1 M1 is ready for release.
*YP 3.1.32 is in QA
*Patch status tags are now checked for by default. Layers which don't wish this can disable the error by removing patch-status from ERROR_QA.
*Several changes have merged for M3:
*Fedora 40 support should be almost complete. GCC 14 is the gift that keeps on giving, the last issue I'm aware of is in 'expect' and there are now two competing patches for that.
**genericarm64 machine (also added to autobuilder)
*Some larger patches are on the list and help reviewing these would be appreciated:
**go upgrade to 1.21.7
**Adding SPDX 3.0 from Joshua
**rust upgrade to 1.75
**Improved CVE tooling from Marta
**change to bmaptool hosting
**bitbake-setup and configuration fragments from Alexander
**using ipk to generate poky-altcfg images with extra space added
*We had some fixes for the install-buildtools script which showed a lack of automated testing for it. Adding some would be an interesting first contribution if anyone is interested.
**6.6.20 stable kernel update
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
**ability to use “extratools” on autobuilder for tests (e.g. imagemagick components)
**Please consider signing this to show support for those changes.
*Changes still needed or under consideration
**Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
**genericarm64 helper artefacts publishing changes
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
**QA screenshot comparison
*Through post release upgrading our patch count reduced again and is now the lowest level since July 2008!
**sstate permissions issue testcase
**go upgrade to 1.22 (tests cleanly on oe-core now, concerns for other layers)
*We are seeing some odd failures, there was a devtool selftest failure (bug 15418 filed) and also an opkg lock issue as we enabled ipk images but that hasn’t recurred (yet). The opkg lock issue has been seen in builds by Khem previously.
*There is a concerning problem when trying to update the CVE database since CPE restrictions don’t always update when changed upstream. This is causing higher numbers of CVEs to be reported on the autobuilder generated charts.
*There have been questions about official RISC-V support in this next release, especially since it is an LTS. We will trial qemuriscv64 support in M3 but remove it before the final LTS release as there is no sponsor for that support.


'''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 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.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
*There are bugs that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_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.
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M3 build date  2024/02/19
*YP 5.0 M3 Release date 2024/03/01
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30
'''Upcoming dot releases:'''<br/>
*YP 4.3.3 was released.
*YP 3.1.32 is in QA.
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.17 build date 2024/03/11
*YP 4.0.17 Release date 2024/03/22
*YP 4.3.4 build date 2024/03/25
*YP 4.3.4 Release date 2024/04/05
*YP 3.1.33 build date 2024/04/15
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.18 build date 2024/04/22
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.19 build date 2024/06/03
*YP 4.0.19 Release date 2024/06/14


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2618 (last week 2633) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2779 (last week 2774) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1155 (last week 1144)
**Total patches found: 1072 (last week 1072)
**Patches in the Pending State: 249 (22%) [last week 250 (22%)]
**Patches in the Pending State: 205 (19%) [last week 205 (19%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 M1 is ready for release.
*YP 5.1 M2 Build date 2024-07-08
*YP 5.1 M2 Release date 2024-07-19
*YP 5.1 M3 Build date 2024-08-26
*YP 5.1 M3 Release date 2024-09-06
*YP 5.1 M4 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25
'''Upcoming dot releases:'''<br/>
*YP 4.0.19 is ready for release.
*YP 5.0.2 Build Date 2024-06-24
*YP 5.0.2 Release Date 2024-07-05
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.20 Release Date 2024-07-26
*YP 5.0.3 Build Date 2024-08-12
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.21 Build Date 2024-09-09
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.22 Release Date 2024-10-25
*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


'''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/>

Revision as of 15:00, 18 June 2024

Yocto Project Weekly Status June 18th, 2024

Current Dev Position: YP 5.1 M2
Next Deadline: YP 5.1 M2 Build 8 July 2024

Next Team Meetings:

Key Status/Updates:

  • YP 4.0.19 is ready for release.
  • YP 5.1 M1 is ready for release.
  • Patch status tags are now checked for by default. Layers which don't wish this can disable the error by removing patch-status from ERROR_QA.
  • Fedora 40 support should be almost complete. GCC 14 is the gift that keeps on giving, the last issue I'm aware of is in 'expect' and there are now two competing patches for that.
  • Some larger patches are on the list and help reviewing these would be appreciated:
    • Adding SPDX 3.0 from Joshua
    • Improved CVE tooling from Marta
    • bitbake-setup and configuration fragments from Alexander
  • We had some fixes for the install-buildtools script which showed a lack of automated testing for it. Adding some would be an interesting first contribution if anyone is interested.
  • There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
    • Please consider signing this to show support for those changes.
    • Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
  • We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
  • Through post release upgrading our patch count reduced again and is now the lowest level since July 2008!

Ways to contribute:

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M1 is ready for release.
  • YP 5.1 M2 Build date 2024-07-08
  • YP 5.1 M2 Release date 2024-07-19
  • YP 5.1 M3 Build date 2024-08-26
  • YP 5.1 M3 Release date 2024-09-06
  • YP 5.1 M4 Build date 2024-09-30
  • YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

  • YP 4.0.19 is ready for release.
  • YP 5.0.2 Build Date 2024-06-24
  • YP 5.0.2 Release Date 2024-07-05
  • YP 4.0.20 Build Date 2024-07-15
  • YP 4.0.20 Release Date 2024-07-26
  • YP 5.0.3 Build Date 2024-08-12
  • YP 5.0.3 Release Date 2024-08-23
  • YP 4.0.21 Build Date 2024-09-09
  • YP 4.0.21 Release Date 2024-09-20
  • YP 5.0.4 Build Date 2024-09-23
  • YP 5.0.4 Release Date 2024-10-04
  • YP 4.0.22 Build Date 2024-10-14
  • YP 4.0.22 Release Date 2024-10-25
  • 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

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=86369"