Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(169 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 5th, 2022 ==
== Yocto Project Weekly Status April 16th, 2024 ==
Current Dev Position: YP 4.1 M2<br/>
Current Dev Position: YP 5.0 preparing to build rc2 <br/>
Next Deadline: 11th July 2022 YP 4.1 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 July 7th 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 July 5th at 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 5.0 rc1 is building but has many (6+) failures in the build so will have to be abandoned.
*Next week M2 is due to build so if anyone has changes for that milestone, please send ASAP.
*The final dunfell build will follow 5.0 into QA.
*YP 4.0.2 has been through QA and is likely to be released in the next few days.
*The master branch has diverged from scarthgap.
*A reproducibility issue was identified and raised a question on whether we could enable              an old QA check for these kinds of issues (‘buildpaths’ in insane.bbclass). Some bugs were fixed in the test but is has highlighted several reproducibility issues. Some have been fixed but others remain:
*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.
**docs issues in lib32-vala, rpm, lib32-gtk-doc, vala, gtk-doc
*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.
**musl issue in ltp
*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.
**multilib issues in lib32-vala, vala, rpm (may overlap docs)
*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.
**qemuarm64 kernel-devsrc issue (Bruce looking into)
*There are patches for improving the build performance graphs in review. Sample output from the changes is here and here.
**meta-virt issues in xen-tools (Christopher looking into)
*There are also patches under review for the patch/cve metrics page to improve the usability.
**meta-gplv2 issues in mc, tar
*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.
**lttng-modules .debug issue on beaglebone, edgerouter, and qemumips
*Fixing these will allow us to enable buildpaths by default which should allow more people to spot reproducibility issues.
*There is a discussion about layer setup tooling in the bitbake-layers discussion on the OE-Core list, input is welcome from those with an interest in this.
*There is also a RFC series about improving the eSDK tooling workflows from Alex Kanavin which may be of interest.
*Code to monitor the /proc/pressure interface has been added and there is a patch to optionally allow bitbake to reduce the number of processes running depending on system load, which it is hoped may help some of our autobuilder intermittent issues (thanks Aryaman and Randy).
*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 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.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 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/>
'''YP 5.0 Milestone Dates:'''<br/>
*YP 4.1 M2 build date 2022/07/11
*YP 5.0 is building
*YP 4.1 M2 Release date 2022/07/22
*YP 5.0 M4 Release date 2024/04/30
*YP 4.1 M3 build date 2022/08/22
 
*YP 4.1 M3 Release date 2022/09/02
'''YP 5.1 Proposed Milestone Dates:'''<br/>
*YP 4.1 M4 build date 2022/10/03
*YP 5.1 M1 Build date 2024-05-20
*YP 4.1 M4 Release date 2022/10/28
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.2 build date 2022/06/27 - pending TSC approval
*YP 4.3.4 is released.
*YP 4.0.2 Release date 2022/07/08
*YP 3.1.33 build date 2024-04-15
*YP 3.1.18 build date 2022/07/18
*YP 3.1.33 Release date 2024-04-26
*YP 3.1.18 Release date 2022/07/29
*YP 4.0.18 build date 2024-04-22
*YP 4.0.3 build date 2022/08/08
*YP 4.0.18 Release date 2024-05-03
*YP 4.0.3 Release date 2022/08/19
*YP 4.0.19 build date 2024-06-03
*YP 3.1.19 build date 2022/08/29
*YP 4.0.19 Release date 2024-06-14
*YP 3.1.19 Release date 2022/09/09
 
*YP 4.0.4 build date 2022/09/19
'''Upcoming Proposed dot releases:'''<br/>
*YP 4.0.4 Release date 2022/09/30
*YP 5.0.1 Build Date 2024-05-13
*YP 3.1.20 build date 2022/10/10
*YP 5.0.1 Release Date 2024-05-24
*YP 3.1.20 Release date 2022/10/21
*YP 5.0.2 Build Date 2024-06-24
*YP 4.0.5 build date 2022/10/31
*YP 5.0.2 Release Date 2024-07-05
*YP 4.0.5 Release date 2022/11/11
*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:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2387 (last week 2400) (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: 1158 (last week 1151)
**Total patches found: 1173 (last week 1174)
**Patches in the Pending State: 328 (28%) [last week 326 (28%)]
**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 67: Line 83:


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

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

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