Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(162 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 17th, 2023 ==
== Yocto Project Weekly Status Nov. 19th, 2024 ==
Current Dev Position: YP 4.2 M2<br/>
Current Dev Position: YP 5.2 M1<br/>
Next Deadline: 23rd January 2023 YP 4.2 M2 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 January 19th 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 January 17th 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.1.2 is in QA
*YP 5.0.5 is under review
*A large number of package upgrades have merged bringing us up to date with various upstreams.
*YP 4.0.23 is in QA
*We have started moving code out of core bbclass files into the function libraries to help reduce parsing memory use, volumes of data transfer and sstate signature data sizes. Help is welcome in developing further patches to improve our function libraries.
*Patch merging is continuing to flow but there are a lot of upgrades pending after the recent AUH run.
*The autobuilder controller has been relocated to deal with connectivity issues, we do have some issues to iron out before things are back to normal service. We were unable to upgrade the buildbot version as there were too many other moving pieces.
*A patch is pending to remove support for BB_DANGLINGAPPENDS_WARNONLY
*We are trying to upgrade uninative to include libgcc to deal with pthread_cancel failures.  Newer versions of patchelf are proving problematic and appear to be causing segfaults and we’re trying to untangle this from other issues.
*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 have reverted the tune for qemux86-64 back to corei7-64 since we still have v2 hardware that won’t work properly with v3 under KVM and similar.
*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
*A uninative bug has been exposed by recent bitbake datastore improvements which could cause sstate to be missed/duplicated.
*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).
*We merged a number of neat rust improvements which add on target cargo support and added automated QA tests for this functionality so we can ensure it continues to work and doesn’t regress. Thanks Alex Kiernan, we hope to see more series like this one!
*The 5.2 development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing
*CVE levels in master are becoming worrying again, help would be appreciated to address the open issues.
*We need to continue to develop this, thanks to all who have contributed so far!
*The autobuilder maintenance window now occurs on Mondays.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''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.
*Help us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*Help us resolve CVE issues: CVE metrics  
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
 
'''Tracking Metrics:'''<br/>
*WDD 2721 (last week 2759) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**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 4.2 Milestone Dates:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
*YP 4.2 M2 build date 2023/01/23
*YP 5.2 M1 Build Date 2024-12-09
*YP 4.2 M2 Release date 2023/02/03
*YP 5.2 M1 Release Date 2024-12-20
*YP 4.2 M3 build date 2023/02/20
*YP 5.2 M2 Build Date 2025-01-20
*YP 4.2 M3 Release date 2023/03/03
*YP 5.2 M2 Release Date 2025-01-31
*YP 4.2 M4 build date 2023/04/03
*YP 5.2 M3 Build Date 2025-03-03
*YP 4.2 M4 Release date 2023/04/28
*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.1.2 ready for release
*YP 5.0.5 is in review.
*YP 3.1.22 built and in QA
*YP 4.0.23 is in QA.
*YP 3.1.22 Release date 2023/01/27
*YP 4.0.23 Release Date 2024-11-29
*YP 4.0.7 build date 2023/01/30
*YP 5.1.1 Build Date 2024-12-02
*YP 4.0.7 Release date 2023/02/10
*YP 5.1.1 Release Date 2024-12-13
*YP 3.1.23 build date 2023/02/13
*YP 5.0.6 Build Date 2024-12-16
*YP 3.1.23 Release date 2023/02/24
*YP 5.0.6 Release Date 2024-12-27
*YP 4.0.8 build date 2023/02/27
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.8 Release date 2023/03/10
*YP 4.0.24 Release Date 2025-01-17
*YP 4.1.3 build date 2023/03/06
*YP 5.1.2 Build Date 2025-01-13
*YP 4.1.3 Release date 2023/03/17
*YP 5.1.2 Release Date 2025-01-24
*YP 3.1.24 build date 2023/03/20
*YP 5.0.7 Build Date 2025-01-27
*YP 3.1.24 Release date 2023/03/31
*YP 5.0.7 Release Date 2025-02-07
*YP 4.0.9 build date 2023/04/10
*YP 4.0.25 Build Date 2025-02-17
*YP 4.0.9 Release date 2023/04/21
*YP 4.0.25 Release Date 2025-02-28
*YP 4.1.4 build date 2023/05/01
*YP 5.1.3 Build Date 2025-02-24
*YP 4.1.4 Release date 2023/05/13
*YP 5.1.3 Release Date 2025-03-07
*YP 3.1.25 build date 2023/05/08
*YP 5.0.8 Build Date 2025-03-10
*YP 3.1.25 Release date 2023/05/19
*YP 5.0.8 Release Date 2025-03-21
*YP 4.0.10 build date 2023/05/15
*YP 5.1.4 Build Date 2025-03-24
*YP 4.0.10 Release date 2023/05/26
*YP 5.1.4 Release Date 2025-04-04
 
*YP 4.0.26 Build Date 2025-04-07
'''Tracking Metrics:'''<br/>
*YP 4.0.26 Release Date 2025-04-18
*WDD 2457 (last week 2447) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.9 Build Date 2025-04-21
*OE-Core/Poky Patch Metrics
*YP 5.0.9 Release Date 2025-05-02
**Total patches found: 1181 (last week 1176)
*YP 4.0.27 Build Date 2025-05-19
**Patches in the Pending State: 279 (24%) [last week 281 (24%)]
*YP 4.0.27 Release Date 2025-05-30
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*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/>
Line 71: 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"