Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(212 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 19th, 2022 ==
== Yocto Project Weekly Status Nov. 19th, 2024 ==
Current Dev Position: YP 4.1 M3<br/>
Current Dev Position: YP 5.2 M1<br/>
Next Deadline: 22nd August 2022 YP 4.1 M3 Build<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 July 21st 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 July 19th at 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 5.0.5 is under review
*YP 4.1 M2 has a build in progress and then will go into QA
*YP 4.0.23 is in QA
*Last week there seemed to be a large number of autobuilder issues including many non-deterministic dependencies for qemu, as well as a lot of intermittent buildpaths issues. These have now mostly been resolved.
*Patch merging is continuing to flow but there are a lot of upgrades pending after the recent AUH run.
*The help received in resolving buildpaths issues was appreciated, particularly with the kernel where we seemed to uncover several unexpectedly.
*A patch is pending to remove support for BB_DANGLINGAPPENDS_WARNONLY
*We have enabled buildpaths in WARN_QA by default. This takes our reproducibility to a new level but there is some fallout in layers which will need to be fixed.
*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.  
*meta-gplv2 builds have been dropped from master and the layer will no longer be maintained.
*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
*We’ve noticed that debug information is still not being processed by package.bbclass entirely correctly and it is missing a large chunk of the kernel sources for example. RP is trying to debug this.
*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).
*There are continued reports of issues with the rust SDK compiler. Sadly we just have patches to make x86_64 work rather than getting to the root of the issues and cross compile it correctly, which is a concern.
*The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
*Work is continuing on the /proc/pressure monitoring code. Initial averaging wasn’t working so well but we have an improved approach which seems to regulate builds better.
*We need to continue to develop this, thanks to all who have contributed so far!
*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
 


'''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 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.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.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 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 M2 Release date 2022/07/22
*WDD 2721 (last week 2759) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.1 M3 build date 2022/08/22
*OE-Core/Poky Patch Metrics
*YP 4.1 M3 Release date 2022/09/02
**Total patches found: 1077 (last week 1070)
*YP 4.1 M4 build date 2022/10/03
**Patches in the Pending State: 178 (17%) [last week 175 (16%)]
*YP 4.1 M4 Release date 2022/10/28
*https://autobuilder.yocto.io/-release/patchmetrics/
 
'''YP 5.2 Milestone Dates:'''<br/>
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.18 build date 2022/07/27
*YP 5.0.5 is in review.
*YP 3.1.18 Release date 2022/08/05
*YP 4.0.23 is in QA.
*YP 4.0.3 build date 2022/08/08
*YP 4.0.23 Release Date 2024-11-29
*YP 4.0.3 Release date 2022/08/19
*YP 5.1.1 Build Date 2024-12-02
*YP 3.1.19 build date 2022/08/29
*YP 5.1.1 Release Date 2024-12-13
*YP 3.1.19 Release date 2022/09/09
*YP 5.0.6 Build Date 2024-12-16
*YP 4.0.4 build date 2022/09/19
*YP 5.0.6 Release Date 2024-12-27
*YP 4.0.4 Release date 2022/09/30
*YP 4.0.24 Build Date 2025-01-06
*YP 3.1.20 build date 2022/10/10
*YP 4.0.24 Release Date 2025-01-17
*YP 3.1.20 Release date 2022/10/21
*YP 5.1.2 Build Date 2025-01-13
*YP 4.0.5 build date 2022/10/31
*YP 5.1.2 Release Date 2025-01-24
*YP 4.0.5 Release date 2022/11/11
*YP 5.0.7 Build Date 2025-01-27
 
*YP 5.0.7 Release Date 2025-02-07
'''Tracking Metrics:'''<br/>
*YP 4.0.25 Build Date 2025-02-17
*WDD 2414 (last week 2397) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0.25 Release Date 2025-02-28
*OE-Core/Poky Patch Metrics
*YP 5.1.3 Build Date 2025-02-24
**Total patches found: 1159 (last week 1155)
*YP 5.1.3 Release Date 2025-03-07
**Patches in the Pending State: 327 (28%) [last week 327 (28%)]
*YP 5.0.8 Build Date 2025-03-10
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status


== 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]]

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