Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(183 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 7th, 2022 ==
== Yocto Project Weekly Status May 21st, 2024 ==
Current Dev Position: YP 4.1 M2<br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: 11th July 2022 YP 4.1 M2 Build<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday June 9th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday May 23rd at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday June 7th at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday May 21st at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday June 14th 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/>
*YP 4.1 M1 was built and been through QA with one kernel issue raised. We will likely release and fix this for M2, pending TSC approval.
*YP 5.0.1 has been through QA and is pending review for release
*YP 3.1.17 rc1 was built but failed on the autobuilder, partly due to infrastructure issues but also failing ptests in openssl, likely due to expired certificates. As of writing,  rc2 is building after infrastructure fixes but the ptest fixes were insufficient. If there are no other issues we will aim to release rc2 and fix the openssl ptest regressions for 3.1.18 pending TSC approval.
*There are some CVE related announcements which are helpful to us:
*Patches have continued to merge into master but have been slowed down by various intermittent issues showing up on the autobuilder:
**There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
**We have bumped the minimum make version for the project and added a make-native dependency for perl to avoid bugs in old make 4.1 versions (particularly on ubuntu 18.04).
**CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
**There are some fixes for potential deadlock issues in the bitbake UI on the bitbake list for review
*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
**We also have some tweaks to the wget fetcher to allow infrastructure mirror races to be avoided.
**Please consider signing this to show support for those changes.
*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
**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.
*The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date. Marta sent out an update last week on this (thanks!)
*gcc 14 has merged to master. There are errors in meta-arm, meta-virtualization and meta-mingw. Now that has merged, we will build and release a new uninative version.
*More of the WORKDIR to UNPACKDIR transition has merged and devtool oe-local-files support has been dropped.
*The next stage of the WORKDIR changes is pending testing in master-next.
*The aim is to build YP 5.1 M1 as soon as the various queued patches stabilize.
*The project is in the process of testing a new way of hosting our autobuilder with plans to switch soon if successful. Our existing hardware is past end of life and showing increased hardware failures so is currently down on capacity meaning builds are taking longer than normal.
*Automated testing continues to show large numbers of problems (e.g. a reproducibility issue in spirv-tools) but we continue to work through and fix issues as quickly as we can.
*Two issues causing failures on the new test infrastructure were tracked down to problems in bitbake. Both were effectively timing related issues.
PR server pass through support merged.
*A rust build issue of x86 hosted builds vs arm hosted builds has been identified as the cause of intermittent failures. Whilst this can be fixed, the fix breaks tests and/or reproducibility which gives challenges given the need to fix scarthgap. There are also challenges upgrading to newer rust versions.
*The performance graph improvements have merged.
*Improvements to the patch and CVE metrics page have also merged.


'''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!
*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 4.1 See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enhancements.2FBugs
*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 us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*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.


'''YP 4.1 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.1 M1 back from QA
*WDD 2752 (last week 2740) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.1 M2 build date 2022/07/11
*OE-Core/Poky Patch Metrics
*YP 4.1 M2 Release date 2022/07/22
**Total patches found: 1127 (last week 1128)
*YP 4.1 M3 build date 2022/08/22
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
*YP 4.1 M3 Release date 2022/09/02
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*YP 4.1 M4 build date 2022/10/03
 
*YP 4.1 M4 Release date 2022/10/28
'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 M1 Build date 2024-05-20
*YP 5.1 M1 Release date 2024-05-31
*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/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.17 build date 2022/06/06
*YP 5.0.1 is ready for release.
*YP 3.1.17 Release date 2022/06/17
*YP 4.0.19 build date 2024-06-03
*YP 4.0.2 build date 2022/06/27
*YP 4.0.19 Release date 2024-06-14
*YP 4.0.2 Release date 2022/07/08
*YP 5.0.2 Build Date 2024-06-24
*YP 3.1.18 build date 2022/07/18
*YP 5.0.2 Release Date 2024-07-05
*YP 3.1.18 Release date 2022/07/29
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.3 build date 2022/08/08
*YP 4.0.20 Release Date 2024-07-26
*YP 4.0.3 Release date 2022/08/19
*YP 5.0.3 Build Date 2024-08-12
*YP 3.1.19 build date 2022/08/29
*YP 5.0.3 Release Date 2024-08-23
*YP 3.1.19 Release date 2022/09/09
*YP 4.0.21 Build Date 2024-09-09
*YP 4.0.4 build date 2022/09/19
*YP 4.0.21 Release Date 2024-09-20
*YP 4.0.4 Release date 2022/09/30
*YP 5.0.4 Build Date 2024-09-23
*YP 3.1.20 build date 2022/10/10
*YP 5.0.4 Release Date 2024-10-04
*YP 3.1.20 Release date 2022/10/21
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.5 build date 2022/10/31
*YP 4.0.22 Release Date 2024-10-25
*YP 4.0.5 Release date 2022/11/11
*YP 5.0.5 Build Date 2024-11-11
 
*YP 5.0.5 Release Date 2024-11-22
'''Tracking Metrics:'''<br/>
*YP 4.0.23 Build Date 2024-11-18
*WDD 2449 (last week 2477 (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0.23 Release Date 2024-11-29
*Poky Patch Metrics
**Total patches found: 1175 (last week 1172)
**Patches in the Pending State: 332 (28%) [last week 331 (28%)]
*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 62: Line 80:


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

Revision as of 14:44, 21 May 2024

Yocto Project Weekly Status May 21st, 2024

Current Dev Position: YP 5.1 M1
Next Deadline: YP 5.1 M1 Build 20 May 2024

Next Team Meetings:

Key Status/Updates:

  • YP 5.0.1 has been through QA and is pending review for release
  • There are some CVE related announcements which are helpful to us:
    • There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
    • CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
  • 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.
  • The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date. Marta sent out an update last week on this (thanks!)
  • gcc 14 has merged to master. There are errors in meta-arm, meta-virtualization and meta-mingw. Now that has merged, we will build and release a new uninative version.
  • More of the WORKDIR to UNPACKDIR transition has merged and devtool oe-local-files support has been dropped.
  • The next stage of the WORKDIR changes is pending testing in master-next.
  • The aim is to build YP 5.1 M1 as soon as the various queued patches stabilize.
  • The project is in the process of testing a new way of hosting our autobuilder with plans to switch soon if successful. Our existing hardware is past end of life and showing increased hardware failures so is currently down on capacity meaning builds are taking longer than normal.
  • Automated testing continues to show large numbers of problems (e.g. a reproducibility issue in spirv-tools) but we continue to work through and fix issues as quickly as we can.
  • Two issues causing failures on the new test infrastructure were tracked down to problems in bitbake. Both were effectively timing related issues.

PR server pass through support merged.

  • A rust build issue of x86 hosted builds vs arm hosted builds has been identified as the cause of intermittent failures. Whilst this can be fixed, the fix breaks tests and/or reproducibility which gives challenges given the need to fix scarthgap. There are also challenges upgrading to newer rust versions.
  • The performance graph improvements have merged.
  • Improvements to the patch and CVE metrics page have also merged.

Ways to contribute:

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M1 Build date 2024-05-20
  • YP 5.1 M1 Release date 2024-05-31
  • 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 5.0.1 is ready for release.
  • YP 4.0.19 build date 2024-06-03
  • YP 4.0.19 Release date 2024-06-14
  • 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