Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(20 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 30th, 2024 ==
== Yocto Project Weekly Status Nov. 19th, 2024 ==
Current Dev Position: YP 5.1 M3 <br/>
Current Dev Position: YP 5.2 M1<br/>
Next Deadline: YP 5.1 M3 Build 26 Aug. 2024<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 Aug. 2nd at 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 30th 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 4.0.20 is due to be released
*YP 5.0.5 is under review
*YP 5.1 M2 is in QA
*YP 4.0.23 is in QA
*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
*Patch merging is continuing to flow but there are a lot of upgrades pending after the recent AUH run.
*SPDX 3.0 has merged and is now the default.
*A patch is pending to remove support for BB_DANGLINGAPPENDS_WARNONLY
*We updated to glibc 2.40, thanks Khem. There is an issue with building pseudo under the new glibc version which is being worked on.
*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.
*We identified an issue which meant warnings/errors in nativesdk recipes were not showing on our autobuilder. We have the fix for the CI issue ready as soon as we fix those warnings/errors, the gcc path problems are proving tricky.
*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 were able to optimize some space usage in builds, thanks Ross. The results are visible on our performance charts, e.g.: https://autobuilder.yocto.io/pub/non-release/20240723-5/testresults/buildperf-alma8/perf-alma8_master_20240723030045_28fd497a26.html https://autobuilder.yocto.io/pub/non-release/20240723-4/testresults/buildperf-debian11/perf-debian11_master_20240722200022_28fd497a26.html
*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).
*Further help on optimizing build disk usage would be most 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
*Some larger patches still need help with review these would be appreciated:
*We need to continue to develop this, thanks to all who have contributed so far!
**Improved CVE tooling from Marta
**kernel fitimage changes from Adrian
**bitbake-setup and configuration fragments from Alexander
*We’ve been trying to resolve some of the longer standing patches in review and are getting more caught up.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*YP 4.0.20 was released
*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!
*YP 5.1 M2 is due to be released
*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
*A new wiki page summarizing options for meta-gplv2 replacement was created: https://wiki.yoctoproject.org/wiki/Meta-gpl2_layer_replacement (thanks Khem)
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*A document giving a brief overview of the Yocto Project Autobuilder/Infrastructure has been shared: https://wiki.yoctoproject.org/wiki/images/0/04/Yocto_Project_Autobuilder.pdf and will be discussed on today’s engineering sync call.
*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
*Autobuilder intermittent issues continue to cause concern but if we don’t have anyone able to work on them there is little we can do.
*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.
*A bug in pseudo around the resolution of symlinks was identified and a fix merged, thanks to the reporter for sending a good test case!
*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.
*We cleaned up a lot of python dependencies and added some extra tests, thanks Ross.
*Help us resolve CVE issues: CVE metrics
*The rustdoc reproducibility issue was found and fixed, thanks Sundeep! We will now be able to upgrade rust to newer versions although further issues remain in some newer versions.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*The new mesa version requires meta-clang for the intel drivers. We need to make a decision on how to handle this, clang is likely to make its way to core at some point but work is needed to make the overrides suitable for core before that can happen.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2798 (last week 2782) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2721 (last week 2759) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1083 (last week 1079)
**Total patches found: 1077 (last week 1070)
**Patches in the Pending State: 179 (16%) [last week 178 (17%)]
**Patches in the Pending State: 178 (17%) [last week 175 (16%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
*YP 5.1 M2 is ready for release.
*YP 5.2 M1 Build Date 2024-12-09
*YP 5.1 M3 Build date 2024-08-26
*YP 5.2 M1 Release Date 2024-12-20
*YP 5.1 M3 Release date 2024-09-06
*YP 5.2 M2 Build Date 2025-01-20
*YP 5.1 M4 Build date 2024-09-30
*YP 5.2 M2 Release Date 2025-01-31
*YP 5.1 M4 Release date 2024-10-25
*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 4.0.20 is released.
*YP 5.0.5 is in review.
*YP 5.0.3 Build Date 2024-08-12
*YP 4.0.23 is in QA.
*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
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

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