Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(58 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status September 12th, 2023 ==
== Yocto Project Weekly Status June 4th, 2024 ==
Current Dev Position: YP 4.3 M4 (Feature Freeze)<br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: 2nd October 2023 YP 4.3 M4 build date<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday September 14th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday June 6th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday September 12th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday June 4th 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 4.3 and 4.3 M3 is in QA
*YP 4.0.19 is in QA
*The numpy reproducibility issue is not solved unfortunately
*YP 5.1 M1 rc1 is building
*There are continuing intermittent ptest issues for openssh and glib-networking amongst other issues
*We identified the performance problem in bitbake using hash equivalence servers and have made changes to batch queries and improve build times
*The testing for qemuppc and qemumips/qemumips64 has been reduced and we’re no longer testing core-image-sato-sdk on these platforms.
*Extra logging for that performance problem is available by setting BB_LOGCONFIG=XXX/bitbake/contrib/autobuilderlog.json (the more verbose logging the autobuilder uses) which will then show if initial query or rehash looping takes longer than 30s for iterations or 60s overall.
*SPDX manifests are now enabled by default for OE-Core/nodistro as well as poky.
*We changed locked-sigs to include the hash equivalence mapping data, removing the need to copy the cache file.
*Patches have been resubmitted to radically alter the do_unpack process for license compliance reasons. The code is complex and hard to understand and will have a performance impact on builds as well as making things hard to debug. *The risk of not taking the changes is that for some legal departments, the SPDX data isn’t detailed enough. The compromise between performance and ease of use vs. legal requirements is a tough one. We don’t really want to have two codepaths either. Feedback/review on the series welcome.
*Libtool was upgraded to the 2.5.0 alpha release, many patches were merged upstream.
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
*Qemu has been upgraded to 9.0.0, kernel headers to 6.9 and stable and dev kernel updates merged (to 6.6.32)
**Marta Rybczynska will be working on the security topic
*There is one remaining issue on fedora40, systemtap-native does not build. The other Fedora 40 are believed to be fixed.
**Alexander Kanvin will be working on the core workflow topic
*Some layers are setting fallbacks for UNPACKDIR which break OE-Core by trying to claim compatibility with everything. Errors have been added to make this problem clear.
**Savoir-faire Linux will be working on the toaster and VSCode topics
*sstate has had changes to fix a bug where build-history data was inconsistent. The siteconfig class was removed to make that change easier and improve the code, it was mostly unused anyway.
**BayLibre will be working on the patchtest and project tooling topics
*The parallelism in the hash client was removed as batching queries is much more effective and easier on the server.
**Michael Opdenacker (Bootlin) will be working on the binary distro topic
*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
**Smile will be working on the meta-openembedded topic area
*Please consider signing this to show support for those changes.
We’d also note that Tim Orling (Konsulko) will be working on the layer index.
*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.
*There is a further update from Marta/Syslinbit on the CVE tooling/patches
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
*Post release upgrading is resulting in an improvement in patch metrics which is great to see, more should appear next week in the statistics too.


'''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 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_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 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 4.3 Milestone Dates:'''<br/>
*YP 4.3 M3 is in QA
*YP 4.3 M4 build date  2023/10/02
*YP 4.3 M4 Release date 2023/10/27
'''Upcoming dot releases:'''<br/>
*YP 3.1.28 build date 2023/09/18
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.13 build date 2023/09/25
*YP 4.0.13 Release date 2023/10/06
*YP 3.1.29 build date 2023/10/30
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.14 build date 2023/11/06
*YP 4.0.14 Release date 2023/11/17
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2530 (last week 2500) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2772 (last week 2772) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1186 (last week 1185)
**Total patches found: 1098 (last week 1121)
**Patches in the Pending State: 255 (22%) [last week 254 (21%)]
**Patches in the Pending State: 205 (19%) [last week 221 (20%)]
*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 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/>
*YP 4.0.19 is in QA.
*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/>
Line 65: Line 76:


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

Latest revision as of 14:49, 4 June 2024

Yocto Project Weekly Status June 4th, 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 4.0.19 is in QA
  • YP 5.1 M1 rc1 is building
  • We identified the performance problem in bitbake using hash equivalence servers and have made changes to batch queries and improve build times
  • Extra logging for that performance problem is available by setting BB_LOGCONFIG=XXX/bitbake/contrib/autobuilderlog.json (the more verbose logging the autobuilder uses) which will then show if initial query or rehash looping takes longer than 30s for iterations or 60s overall.
  • We changed locked-sigs to include the hash equivalence mapping data, removing the need to copy the cache file.
  • Libtool was upgraded to the 2.5.0 alpha release, many patches were merged upstream.
  • Qemu has been upgraded to 9.0.0, kernel headers to 6.9 and stable and dev kernel updates merged (to 6.6.32)
  • There is one remaining issue on fedora40, systemtap-native does not build. The other Fedora 40 are believed to be fixed.
  • Some layers are setting fallbacks for UNPACKDIR which break OE-Core by trying to claim compatibility with everything. Errors have been added to make this problem clear.
  • sstate has had changes to fix a bug where build-history data was inconsistent. The siteconfig class was removed to make that change easier and improve the code, it was mostly unused anyway.
  • The parallelism in the hash client was removed as batching queries is much more effective and easier on the server.
  • 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.
  • There is a further update from Marta/Syslinbit on the CVE tooling/patches
  • We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
  • Post release upgrading is resulting in an improvement in patch metrics which is great to see, more should appear next week in the statistics too.

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 4.0.19 is in QA.
  • 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