Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(89 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status September 26th, 2023 ==
== Yocto Project Weekly Status Nov. 19th, 2024 ==
Current Dev Position: YP 4.3 M4 (Feature Freeze)<br/>
Current Dev Position: YP 5.2 M1<br/>
Next Deadline: 2nd October 2023 YP 4.3 M4 build date<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 September 28st 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Nov. 21st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday September 26th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync Tuesday Nov. 19th 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 4.3 M3 rc1 was released and work is being done on the autobuilder QA email step to improve for future releases. The regression report is still being worked on.
*YP 5.0.5 is under review
*YP 3.1.28 is under review for release
*YP 4.0.23 is in QA
*YP 4.0.13 rc2 is in QA
*Patch merging is continuing to flow but there are a lot of upgrades pending after the recent AUH run.
*The numpy reproducibility issue remains and is proving extremely problematic with many failed builds. We may have to merge the debug patch into master.
*A patch is pending to remove support for BB_DANGLINGAPPENDS_WARNONLY
*The openssh ptest intermittent failure does have better logs available but we’ve yet to decode what it means: http://autobuilder.yocto.io/pub/non-release/20230917-2/testresults/qemuarm64-ptest/openssh.log
*Yocto Project Compatible (and hence yocto-check-layer) is potentially undergoing some small tweaks which includes checking for SECURITY files in repository top levels, checking for network access outside do_fetch as part of normal builds and checking for disabled QA checks.  
*The changes to error for overlapping symlinks under sstate control have highlighted some issues, particularly in world build configurations however so far these have proven to be real issues that needed addressing in the configuration as the files overlapped and caused determinism issues.
*A potential new “include_all” conf file directive (discussed on the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2055 ) has no strong objections and is proceeding to proof of concept
*The number of build failures from incoming patches remains high and is causing patch review delays and headaches for the maintainers. We are not here to debug people’s patches, we’re only meant to be catching accidental/occasional issues.
*There are patches under review for the addition of configuration fragment management to bitbake. It does require the addition of support for ‘/’ characters in variable flag names (which has been requested in the past too).
*Patches for enabling wider SPDX tooling and testing in core are being proposed but there are quite a few python module dependencies. We do have good tooling/class support for python modules so the maintenance overhead of these is relatively low but the number of modules in core has increased steadily. Feedback welcome.
*The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
*Since the 6.4 kernel is already EOL, we are considering a 6.5 kernel for 4.3 as the best of several difficult options.
*We need to continue to develop this, thanks to all who have contributed so far!
*The project is working on improving its security processes and policies, there are emails on the mailing list discussing this. Please highlight these to any parties who may be interested or have useful feedback.


'''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 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 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.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.
*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.
Line 29: Line 29:
*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/>
'''Tracking Metrics:'''<br/>
*YP 4.3 M3 was released.
*WDD 2721 (last week 2759) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.3 M4 build date  2023/10/02
*OE-Core/Poky Patch Metrics
*YP 4.3 M4 Release date 2023/10/27
**Total patches found: 1077 (last week 1070)
**Patches in the Pending State: 178 (17%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.0 Milestone Dates:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
*YP 5.0 M1 build date 2023/12/04
*YP 5.2 M1 Build Date 2024-12-09
*YP 5.0 M1 Release date 2023/12/15
*YP 5.2 M1 Release Date 2024-12-20
*YP 5.0 M2 build date  2024/01/15
*YP 5.2 M2 Build Date 2025-01-20
*YP 5.0 M2 Release date 2024/01/24
*YP 5.2 M2 Release Date 2025-01-31
*YP 5.0 M3 build date  2024/02/19
*YP 5.2 M3 Build Date 2025-03-03
*YP 5.0 M3 Release date 2024/03/01
*YP 5.2 M3 Release Date 2025-03-14
*YP 5.0 M4 build date  2024/04/01
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.0 M4 Release date 2024/04/30
*YP 5.2 M4 Release Date 2025-04-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.28 is ready for release
*YP 5.0.5 is in review.
*YP 4.0.13 is in QA
*YP 4.0.23 is in QA.
*YP 3.1.29 build date 2023/10/30
*YP 4.0.23 Release Date 2024-11-29
*YP 3.1.29 Release date 2023/11/10
*YP 5.1.1 Build Date 2024-12-02
*YP 4.0.14 build date 2023/11/06
*YP 5.1.1 Release Date 2024-12-13
*YP 4.0.14 Release date 2023/11/17
*YP 5.0.6 Build Date 2024-12-16
*YP 4.2.4 build date 2023/11/13
*YP 5.0.6 Release Date 2024-12-27
*YP 4.2.4 Release date 2023/11/24
*YP 4.0.24 Build Date 2025-01-06
*YP 4.3.1 build date 2023/11/27
*YP 4.0.24 Release Date 2025-01-17
*YP 4.3.1 Release date 2023/12/08
*YP 5.1.2 Build Date 2025-01-13
*YP 3.1.30 build date 2023/12/11
*YP 5.1.2 Release Date 2025-01-24
*YP 3.1.30 Release date 2023/12/22
*YP 5.0.7 Build Date 2025-01-27
*YP 4.0.15 build date 2023/12/18
*YP 5.0.7 Release Date 2025-02-07
*YP 4.0.15 Release date 2023/12/29
*YP 4.0.25 Build Date 2025-02-17
*YP 4.3.2 build date 2024/01/08
*YP 4.0.25 Release Date 2025-02-28
*YP 4.3.2 Release date 2024/01/19
*YP 5.1.3 Build Date 2025-02-24
*YP 3.1.31 build date 2024/01/22
*YP 5.1.3 Release Date 2025-03-07
*YP 3.1.31 Release date 2024/02/02
*YP 5.0.8 Build Date 2025-03-10
*YP 4.0.16 build date 2024/01/29
*YP 5.0.8 Release Date 2025-03-21
*YP 4.0.16 Release date 2024/02/09
*YP 5.1.4 Build Date 2025-03-24
*YP 4.3.3 build date 2024/02/12
*YP 5.1.4 Release Date 2025-04-04
*YP 4.3.3 Release date 2024/02/23
*YP 4.0.26 Build Date 2025-04-07
*YP 3.1.32 build date 2024/03/04
*YP 4.0.26 Release Date 2025-04-18
*YP 3.1.32 Release date 2024/03/15
*YP 5.0.9 Build Date 2025-04-21
*YP 4.0.17 build date 2024/03/11
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.17 Release date 2024/03/22
*YP 4.0.27 Build Date 2025-05-19
*YP 4.3.4 build date 2024/03/25
*YP 4.0.27 Release Date 2025-05-30
*YP 4.3.4 Release date 2024/04/05
*YP 5.0.10 Build Date 2025-06-02
*YP 3.1.33 build date 2024/04/15
*YP 5.0.10 Release Date 2025-06-13
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.18 build date 2024/04/22
*YP 4.0.28 Release Date 2025-07-11
*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/>
*WDD 2475 (last week 2505) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1183 (last week 1185)
**Patches in the Pending State: 254 (21%) [last week 255 (22%)]
*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 91: Line 83:


== 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 15:43, 19 November 2024

Yocto Project Weekly Status Nov. 19th, 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 5.0.5 is under review
  • YP 4.0.23 is in QA
  • Patch merging is continuing to flow but there are a lot of upgrades pending after the recent AUH run.
  • A patch is pending to remove support for BB_DANGLINGAPPENDS_WARNONLY
  • Yocto Project Compatible (and hence yocto-check-layer) is potentially undergoing some small tweaks which includes checking for SECURITY files in repository top levels, checking for network access outside do_fetch as part of normal builds and checking for disabled QA checks.
  • A potential new “include_all” conf file directive (discussed on the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2055 ) has no strong objections and is proceeding to proof of concept
  • There are patches under review for the addition of configuration fragment management to bitbake. It does require the addition of support for ‘/’ characters in variable flag names (which has been requested in the past too).
  • The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
  • We need to continue to develop this, thanks to all who have contributed so far!

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 5.0.5 is in review.
  • YP 4.0.23 is in QA.
  • 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=86498"