Weekly Status: Difference between revisions

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


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday May 23rd 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 May 21st 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/>
*YP 5.0.1 has been through QA and is pending review for release
*YP 4.0.19 has been through QA and is due for release
*There are some CVE related announcements which are helpful to us:
*YP 5.1 M1 rc2 is in QA
**There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
*RFC patches for the CVE tooling changes have been posted, help in review is appreciated
**CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
*There are SPDX 3.0 patches ready for review on the mailing list
*There are patches proposing that missing patch Upstream-Status entries be a fatal QA error, this is likely to merge soon as there have been no objections to it.
*We have a fix for the final Fedora 40 issue, thanks Victor.
*We appreciate everyone fixing layers to work with master after recent changes, the autobuilder health is looking greener, thanks!
*The copy_unihashes function was dropped from bitbake after the locked signature file improvements which simplifies further tooling work
*There is discussion on openembedded-architecture about the details around  configuration fragment tooling potentially being integrated into bitbake
*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
*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.
*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.
*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!)
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
*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.
*Through post release upgrading our patch count reduced again and is now the lowest level since July 2008!
*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/>
Line 39: Line 34:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2752 (last week 2740) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2774 (last week 2772) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1127 (last week 1128)
**Total patches found: 1072 (last week 1098)
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
**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 Milestone Dates:'''<br/>
*YP 5.1 M1 Build date 2024-05-20
*YP 5.1 M1 is in QA
*YP 5.1 M1 Release date 2024-05-31
*YP 5.1 M1 Release date 2024-05-31
*YP 5.1 M2 Build date 2024-07-08
*YP 5.1 M2 Build date 2024-07-08
Line 56: Line 51:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.1 is ready for release.
*YP 4.0.19 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 Build Date 2024-06-24
*YP 5.0.2 Release Date 2024-07-05
*YP 5.0.2 Release Date 2024-07-05

Revision as of 14:49, 11 June 2024

Yocto Project Weekly Status June 11th, 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 has been through QA and is due for release
  • YP 5.1 M1 rc2 is in QA
  • RFC patches for the CVE tooling changes have been posted, help in review is appreciated
  • There are SPDX 3.0 patches ready for review on the mailing list
  • There are patches proposing that missing patch Upstream-Status entries be a fatal QA error, this is likely to merge soon as there have been no objections to it.
  • We have a fix for the final Fedora 40 issue, thanks Victor.
  • We appreciate everyone fixing layers to work with master after recent changes, the autobuilder health is looking greener, thanks!
  • The copy_unihashes function was dropped from bitbake after the locked signature file improvements which simplifies further tooling work
  • There is discussion on openembedded-architecture about the details around configuration fragment tooling potentially being integrated into bitbake
  • 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 in QA
  • 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 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