Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(52 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 29th, 2023 ==
== Yocto Project Weekly Status April 16th, 2024 ==
Current Dev Position: YP 4.3 M3<br/>
Current Dev Position: YP 5.0 preparing to build rc2 <br/>
Next Deadline: 28th August 2023 YP 4.3 M3 build date<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday August 31st 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 August 29th 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/>
*We are now a week away from feature freeze for 4.3.
*YP 5.0 rc1 is building but has many (6+) failures in the build so will have to be abandoned.
*YP 4.0.12 is pending TSC approval and due to release
*The final dunfell build will follow 5.0 into QA.
*YP 4.2.3 is in QA
*The master branch has diverged from scarthgap.
*We merged the 6.4 kernel and were able to resolve the preempt-rt issue (thanks Paul!) however intermittent hangs on qemuppc still remain as well as questions of x86 reliability on the autobuilder.
*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.
*There are patches pending which remove source control revisions from PV and move them to PKGV, further simplifying WORKDIR paths and generally improving the code and the way AUTOREV works. This allows SRCPV to be removed as it is no longer needed. We believe all review discussion has been resolved at this point.
*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.
*Intermittent autobuilder issues, autobuilder hardware problems and large numbers of very intensive rebuilds with low sstate reuse are causing challenges in keeping patches flowing. Some intermittent issues were identified and resolved.
*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.
*Glibc 2.38 merged and a new uninative release was made.
*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 continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
*There are patches for improving the build performance graphs in review. Sample output from the changes is here and here.
*CVE metrics are still high but much reduced for master, thanks!
*There are also patches under review for the patch/cve metrics page to improve the usability.
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
*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.
**Marta Rybczynska will be working on the security topic
**Alexander Kanvin will be working on the core workflow topic
*Other topic areas will likely be announced soon too.


'''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.
Line 32: Line 29:
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''YP 4.3 Milestone Dates:'''<br/>
'''YP 5.0 Milestone Dates:'''<br/>
*YP 4.3 M3 build date 2023/08/28
*YP 5.0 is building
*YP 4.3 M3 Release date 2023/09/08
*YP 5.0 M4 Release date 2024/04/30
*YP 4.3 M4 build date 2023/10/02
 
*YP 4.3 M4 Release date 2023/10/27
'''YP 5.1 Proposed Milestone Dates:'''<br/>
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.12 is released
*YP 4.3.4 is released.
*YP 4.2.3 is ready for release
*YP 3.1.33 build date 2024-04-15
*YP 3.1.28 build date 2023/09/18
*YP 3.1.33 Release date 2024-04-26
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.18 build date 2024-04-22
*YP 4.0.13 build date 2023/09/25
*YP 4.0.18 Release date 2024-05-03
*YP 4.0.13 Release date 2023/10/06
*YP 4.0.19 build date 2024-06-03
*YP 3.1.29 build date 2023/10/30
*YP 4.0.19 Release date 2024-06-14
*YP 3.1.29 Release date 2023/11/10
 
*YP 4.0.14 build date 2023/11/06
'''Upcoming Proposed dot releases:'''<br/>
*YP 4.0.14 Release date 2023/11/17
*YP 5.0.1 Build Date 2024-05-13
*YP 4.2.4 build date 2023/11/13
*YP 5.0.1 Release Date 2024-05-24
*YP 4.2.4 Release date 2023/11/24
*YP 5.0.2 Build Date 2024-06-24
*YP 3.1.30 build date 2023/12/11
*YP 5.0.2 Release Date 2024-07-05
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.15 build date 2023/12/18
*YP 4.0.20 Release Date 2024-07-26
*YP 4.0.15 Release date 2023/12/29
*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 2500 (last week 2488) (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: 1188 (last week 1183)
**Total patches found: 1173 (last week 1174)
**Patches in the Pending State: 258 (22%) [last week 258 (22%)]
**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]]
*[[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

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