Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(152 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 10th, 2023 ==
== Yocto Project Weekly Status Sept. 10th, 2024 ==
Current Dev Position: YP 4.2 M2<br/>
Current Dev Position: YP 5.1 Feature Freeze and Bug Fixing<br/>
Next Deadline: 23rd January 2023 YP 4.2 M2 Build<br/>
Next Deadline: YP 5.1 M4 Build 30 Sept. 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday January 12th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Sept. 12th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday January 10th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync Tuesday Sept. 10th 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.1 M3 is due to be released
*A large number of package upgrades have merged bringing us up to date with various upstreams.
*YP 4.0.21 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.
*We are now at feature freeze and working on bug fixing for the final 5.1 release builds
*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.
*Due to timing of autobuilder infrastructure changes, vacations, no release blocking bugs and also seemingly limited availability of people to help with general bug fixing, we are considering an early M4 build, maybe even this week. If that would cause problems for anyone, please let Richard/the TSC know ASAP.
*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.
*Support for TCLIBCAPPEND was dropped.
*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.
*We updated to only support the “styhead” layer series namespace.
*A uninative bug has been exposed by recent bitbake datastore improvements which could cause sstate to be missed/duplicated.
*The new autobuilder infrastructure is showing a number of challenges including some new bugs, new intermittent issues, challenges with new distros and a new reproducibility issue but we’re working through them
*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!
*There is discussion around configuration file markup/syntax related to fragment management on the architecture list, targeting 5.2.
*CVE levels in master are becoming worrying again, help would be appreciated to address the open issues.
*Upcoming Event:  For those attending OSS EU in Vienna, Yocto Project Developer Day Sept. 19th 9am-5pm. 
*The autobuilder maintenance window now occurs on Mondays.
*Register here: https://events.linuxfoundation.org/open-source-summit-europe/features/co-located-events/#yocto-project-developer-day
*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.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 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 2734 (last week 2764) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1067 (last week 1057)
**Patches in the Pending State: 176 (16%) [last week 177 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 4.2 Milestone Dates:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 4.2 M2 build date 2023/01/23
*YP 5.1 M3 is ready for release.
*YP 4.2 M2 Release date 2023/02/03
*YP 5.1 M4 Build date 2024-09-30
*YP 4.2 M3 build date 2023/02/20
*YP 5.1 M4 Release date 2024-10-25
*YP 4.2 M3 Release date 2023/03/03
*YP 4.2 M4 build date 2023/04/03
*YP 4.2 M4 Release date 2023/04/28


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.1.2 built and in QA
*YP 4.0.21 is in QA.
*YP 4.1.2 Release date 2023/01/20
*YP 5.0.4 Build Date 2024-09-23
*YP 3.1.22 build date 2023/01/16
*YP 5.0.4 Release Date 2024-10-04
*YP 3.1.22 Release date 2023/01/27
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.7 build date 2023/01/30
*YP 4.0.22 Release Date 2024-10-25
*YP 4.0.7 Release date 2023/02/10
*YP 5.0.5 Build Date 2024-11-11
*YP 3.1.23 build date 2023/02/13
*YP 5.0.5 Release Date 2024-11-22
*YP 3.1.23 Release date 2023/02/24
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.8 build date 2023/02/27
*YP 4.0.23 Release Date 2024-11-29
*YP 4.0.8 Release date 2023/03/10
*YP 4.1.3 build date 2023/03/06
*YP 4.1.3 Release date 2023/03/17
*YP 3.1.24 build date 2023/03/20
*YP 3.1.24 Release date 2023/03/31
*YP 4.0.9 build date 2023/04/10
*YP 4.0.9 Release date 2023/04/21
*YP 4.1.4 build date 2023/05/01
*YP 4.1.4 Release date 2023/05/13
*YP 3.1.25 build date 2023/05/08
*YP 3.1.25 Release date 2023/05/19
*YP 4.0.10 build date 2023/05/15
*YP 4.0.10 Release date 2023/05/26
 
'''Tracking Metrics:'''<br/>
*WDD 2447 (last week 2457) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1176 (last week 1189)
**Patches in the Pending State: 281 (24%) [last week 282 (24%)]
*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 72: Line 57:


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

Revision as of 14:51, 10 September 2024

Yocto Project Weekly Status Sept. 10th, 2024

Current Dev Position: YP 5.1 Feature Freeze and Bug Fixing
Next Deadline: YP 5.1 M4 Build 30 Sept. 2024

Next Team Meetings:

Key Status/Updates:

  • YP 5.1 M3 is due to be released
  • YP 4.0.21 is in QA
  • We are now at feature freeze and working on bug fixing for the final 5.1 release builds
  • Due to timing of autobuilder infrastructure changes, vacations, no release blocking bugs and also seemingly limited availability of people to help with general bug fixing, we are considering an early M4 build, maybe even this week. If that would cause problems for anyone, please let Richard/the TSC know ASAP.
  • Support for TCLIBCAPPEND was dropped.
  • We updated to only support the “styhead” layer series namespace.
  • The new autobuilder infrastructure is showing a number of challenges including some new bugs, new intermittent issues, challenges with new distros and a new reproducibility issue but we’re working through them
  • There is discussion around configuration file markup/syntax related to fragment management on the architecture list, targeting 5.2.
  • Upcoming Event: For those attending OSS EU in Vienna, Yocto Project Developer Day Sept. 19th 9am-5pm.
  • Register here: https://events.linuxfoundation.org/open-source-summit-europe/features/co-located-events/#yocto-project-developer-day

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.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.
  • 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.1 Milestone Dates:

  • YP 5.1 M3 is ready for release.
  • YP 5.1 M4 Build date 2024-09-30
  • YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

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

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86442"