Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(118 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 10th, 2023 ==
== Yocto Project Weekly Status April 16th, 2024 ==
Current Dev Position: YP 4.2 M2<br/>
Current Dev Position: YP 5.0 preparing to build rc2 <br/>
Next Deadline: 23rd January 2023 YP 4.2 M2 Build<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<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 April 11th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday January 10th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday April 9th at 8 am PDT (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 rc1 is building but has many (6+) failures in the build so will have to be abandoned.
*A large number of package upgrades have merged bringing us up to date with various upstreams.
*The final dunfell build will follow 5.0 into 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.
*The master branch has diverged from scarthgap.
*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.
*For 5.0, we were able to switch to the new hash equivalence server however the need for websockets complicated the worker configuration and needed new buildtools tarball versions which are causing various problems.
*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.
*During the rc1 build as well as pip and setuptools issues within buildtools, we also saw a qemuppc boot issue, an instance of the spdx dependency problem, an sstate mirror issue and a github network error. This highlights how important fixing these is over the release cycle. The volume of these may impact our ability to maintain the LTS.
*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.
*Thanks to everyone who sent documentation patches, we’re in much better shape with the migration guide and release notes now. Further improvements are still very welcome.
*A uninative bug has been exposed by recent bitbake datastore improvements which could cause sstate to be missed/duplicated.
*The “Binary Distro” work is now well underway and there are PR Server passthrough and image testing patches under review. The wiki page has had a number of policy/process proposals documented, help is welcome to help improve these, or highlight where further documentation is needed.
*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 are patches for improving the build performance graphs in review. Sample output from the changes is here and here.
*CVE levels in master are becoming worrying again, help would be appreciated to address the open issues.
*There are also patches under review for the patch/cve metrics page to improve the usability.
*The autobuilder maintenance window now occurs on Mondays.
*We continue to watch the NIST NVD (CVE database) situation, the recent update didn’t clarify much. Unfortunately there doesn’t appear to be a clear path forward as yet but using data directly from MITRE may help give partial information. These issues are making it hard to know what to include in the 5.0 release as it isn’t clear which changes are security related.
*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 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.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_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.
 
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 is building
*YP 5.0 M4 Release date 2024/04/30


'''YP 4.2 Milestone Dates:'''<br/>
'''YP 5.1 Proposed Milestone Dates:'''<br/>
*YP 4.2 M2 build date 2023/01/23
*YP 5.1 M1 Build date 2024-05-20
*YP 4.2 M2 Release date 2023/02/03
*YP 5.1 M1 Release date 2024-05-31
*YP 4.2 M3 build date 2023/02/20
*YP 5.1 M2 Build date 2024-07-08
*YP 4.2 M3 Release date 2023/03/03
*YP 5.1 M2 Release date 2024-07-19
*YP 4.2 M4 build date 2023/04/03
*YP 5.1 M3 Build date 2024-08-26
*YP 4.2 M4 Release date 2023/04/28
*YP 5.1 M3 Release date 2024-09-06
*YP 5.1 M4 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.1.2 built and in QA
*YP 4.3.4 is released.
*YP 4.1.2 Release date 2023/01/20
*YP 3.1.33 build date 2024-04-15
*YP 3.1.22 build date 2023/01/16
*YP 3.1.33 Release date 2024-04-26
*YP 3.1.22 Release date 2023/01/27
*YP 4.0.18 build date 2024-04-22
*YP 4.0.7 build date 2023/01/30
*YP 4.0.18 Release date 2024-05-03
*YP 4.0.7 Release date 2023/02/10
*YP 4.0.19 build date 2024-06-03
*YP 3.1.23 build date 2023/02/13
*YP 4.0.19 Release date 2024-06-14
*YP 3.1.23 Release date 2023/02/24
 
*YP 4.0.8 build date 2023/02/27
'''Upcoming Proposed dot releases:'''<br/>
*YP 4.0.8 Release date 2023/03/10
*YP 5.0.1 Build Date 2024-05-13
*YP 4.1.3 build date 2023/03/06
*YP 5.0.1 Release Date 2024-05-24
*YP 4.1.3 Release date 2023/03/17
*YP 5.0.2 Build Date 2024-06-24
*YP 3.1.24 build date 2023/03/20
*YP 5.0.2 Release Date 2024-07-05
*YP 3.1.24 Release date 2023/03/31
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.9 build date 2023/04/10
*YP 4.0.20 Release Date 2024-07-26
*YP 4.0.9 Release date 2023/04/21
*YP 5.0.3 Build Date 2024-08-12
*YP 4.1.4 build date 2023/05/01
*YP 5.0.3 Release Date 2024-08-23
*YP 4.1.4 Release date 2023/05/13
*YP 4.0.21 Build Date 2024-09-09
*YP 3.1.25 build date 2023/05/08
*YP 4.0.21 Release Date 2024-09-20
*YP 3.1.25 Release date 2023/05/19
*YP 5.0.4 Build Date 2024-09-23
*YP 4.0.10 build date 2023/05/15
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.10 Release date 2023/05/26
*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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2447 (last week 2457) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2719 (last week 2696) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1176 (last week 1189)
**Total patches found: 1173 (last week 1174)
**Patches in the Pending State: 281 (24%) [last week 282 (24%)]
**Patches in the Pending State: 249 (21%) [last week 249 (21%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


Line 72: 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]]

Revision as of 14:37, 16 April 2024

Yocto Project Weekly Status April 16th, 2024

Current Dev Position: YP 5.0 preparing to build rc2
Next Deadline: 1st April 2024 YP 5.0 M4 build

Next Team Meetings:

Key Status/Updates:

  • YP 5.0 rc1 is building but has many (6+) failures in the build so will have to be abandoned.
  • The final dunfell build will follow 5.0 into QA.
  • The master branch has diverged from scarthgap.
  • For 5.0, we were able to switch to the new hash equivalence server however the need for websockets complicated the worker configuration and needed new buildtools tarball versions which are causing various problems.
  • During the rc1 build as well as pip and setuptools issues within buildtools, we also saw a qemuppc boot issue, an instance of the spdx dependency problem, an sstate mirror issue and a github network error. This highlights how important fixing these is over the release cycle. The volume of these may impact our ability to maintain the LTS.
  • Thanks to everyone who sent documentation patches, we’re in much better shape with the migration guide and release notes now. Further improvements are still very welcome.
  • The “Binary Distro” work is now well underway and there are PR Server passthrough and image testing patches under review. The wiki page has had a number of policy/process proposals documented, help is welcome to help improve these, or highlight where further documentation is needed.
  • There are patches for improving the build performance graphs in review. Sample output from the changes is here and here.
  • There are also patches under review for the patch/cve metrics page to improve the usability.
  • We continue to watch the NIST NVD (CVE database) situation, the recent update didn’t clarify much. Unfortunately there doesn’t appear to be a clear path forward as yet but using data directly from MITRE may help give partial information. These issues are making it hard to know what to include in the 5.0 release as it isn’t clear which changes are security related.

Ways to contribute:

YP 5.0 Milestone Dates:

  • YP 5.0 is building
  • YP 5.0 M4 Release date 2024/04/30

YP 5.1 Proposed Milestone Dates:

  • YP 5.1 M1 Build date 2024-05-20
  • YP 5.1 M1 Release date 2024-05-31
  • YP 5.1 M2 Build date 2024-07-08
  • YP 5.1 M2 Release date 2024-07-19
  • YP 5.1 M3 Build date 2024-08-26
  • YP 5.1 M3 Release date 2024-09-06
  • YP 5.1 M4 Build date 2024-09-30
  • YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

  • YP 4.3.4 is released.
  • YP 3.1.33 build date 2024-04-15
  • YP 3.1.33 Release date 2024-04-26
  • YP 4.0.18 build date 2024-04-22
  • 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

Upcoming Proposed dot releases:

  • YP 5.0.1 Build Date 2024-05-13
  • YP 5.0.1 Release Date 2024-05-24
  • YP 5.0.2 Build Date 2024-06-24
  • YP 5.0.2 Release Date 2024-07-05
  • YP 4.0.20 Build Date 2024-07-15
  • YP 4.0.20 Release Date 2024-07-26
  • YP 5.0.3 Build Date 2024-08-12
  • 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

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives