Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 9: Line 9:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now a week away from feature freeze for 4.3.
*We are now at feature freeze for 4.3.
*YP 4.0.12 is pending TSC approval and due to release
*YP 4.0.12 was released
*YP 4.2.3 is in QA
*YP 4.2.3 is due to be released
*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.
*The qemuppc ssh command hangs continues to be a mystery. It seems to be something in recent master that regressed it but it isn’t the kernel, the binutils upgrade, systemd or glibc or qemu. We’ve not seen any other hangs so the x86 issues may have been something else.
*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.
*The acl/xattr changes are blocked on a hard requirement on tar 1.35, it is unclear how we’d achieve that in all cases.
*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.
*Patches have been resubmitted to radically alter the do_unpack process for license compliance reasons. The code is complex and hard to understand and will have a performance impact on builds as well as making things hard to debug. The risk of not taking the changes is that for some legal departments, the SPDX data isn’t detailed enough. The compromise between performance and ease of use vs. legal requirements is a tough one. We don’t really want to have two codepaths either. Feedback/review on the series welcome.
*Glibc 2.38 merged and a new uninative release was made.
*We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
*We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
*CVE metrics are still high but much reduced for master, thanks!
*The M3 build will depend upon reaching conclusions in several of these areas
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
**Marta Rybczynska will be working on the security topic
**Marta Rybczynska will be working on the security topic
**Alexander Kanvin will be working on the core workflow topic  
**Alexander Kanvin will be working on the core workflow topic  
*Other topic areas will likely be announced soon too.
**Savoir-faire Linux will be working on the toaster and VSCode topics
**BayLibre will be working on the patchtest and project tooling topics
The other remaining topic areas should be announced soon.
We’d also note that Tim Orling (Konsulko) will be working on the layer index.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>

Revision as of 14:50, 29 August 2023

Yocto Project Weekly Status August 29th, 2023

Current Dev Position: YP 4.3 Feature Freeze
Next Deadline: 28th August 2023 YP 4.3 M3 build date

Next Team Meetings:

Key Status/Updates:

  • We are now at feature freeze for 4.3.
  • YP 4.0.12 was released
  • YP 4.2.3 is due to be released
  • The qemuppc ssh command hangs continues to be a mystery. It seems to be something in recent master that regressed it but it isn’t the kernel, the binutils upgrade, systemd or glibc or qemu. We’ve not seen any other hangs so the x86 issues may have been something else.
  • The acl/xattr changes are blocked on a hard requirement on tar 1.35, it is unclear how we’d achieve that in all cases.
  • Patches have been resubmitted to radically alter the do_unpack process for license compliance reasons. The code is complex and hard to understand and will have a performance impact on builds as well as making things hard to debug. The risk of not taking the changes is that for some legal departments, the SPDX data isn’t detailed enough. The compromise between performance and ease of use vs. legal requirements is a tough one. We don’t really want to have two codepaths either. Feedback/review on the series welcome.
  • We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
  • The M3 build will depend upon reaching conclusions in several of these areas
  • We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
    • Marta Rybczynska will be working on the security topic
    • Alexander Kanvin will be working on the core workflow topic
    • Savoir-faire Linux will be working on the toaster and VSCode topics
    • BayLibre will be working on the patchtest and project tooling topics

The other remaining topic areas should be announced soon. We’d also note that Tim Orling (Konsulko) will be working on the layer index.

Ways to contribute:

YP 4.3 Milestone Dates:

  • YP 4.3 M3 build date 2023/08/28
  • YP 4.3 M3 Release date 2023/09/08
  • YP 4.3 M4 build date 2023/10/02
  • YP 4.3 M4 Release date 2023/10/27

Upcoming dot releases:

  • YP 4.0.12 is released
  • YP 4.2.3 is ready for release
  • YP 3.1.28 build date 2023/09/18
  • YP 3.1.28 Release date 2023/09/29
  • YP 4.0.13 build date 2023/09/25
  • YP 4.0.13 Release date 2023/10/06
  • YP 3.1.29 build date 2023/10/30
  • YP 3.1.29 Release date 2023/11/10
  • YP 4.0.14 build date 2023/11/06
  • YP 4.0.14 Release date 2023/11/17
  • YP 4.2.4 build date 2023/11/13
  • YP 4.2.4 Release date 2023/11/24
  • YP 3.1.30 build date 2023/12/11
  • YP 3.1.30 Release date 2023/12/22
  • YP 4.0.15 build date 2023/12/18
  • YP 4.0.15 Release date 2023/12/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=85897"