Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(598 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status December 17, 2019 ==
== Yocto Project Status 28 April 2026 ==
Current Dev Position: YP 3.1 M2 <br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 3.1 M2 build date 1/20/2020<br/>
Next Deadline: YP 6.0 Release Date w/c 2026-05-04<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Dec. 19th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting - Thursday 30th Apr. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Jan. 7th  at 8am PDT (https://zoom.us/j/990892712)
*Weekly Project Engineering Sync - Tuesday 29th Apr. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Dec. 17th at 8am PDT (https://zoom.us/j/990892712)
*Yocto Project Patch Review - Thursday 30th Apr. 10am GMT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Twitch - Next event is Tuesday Dec. 17th at 8am PDT (https://www.twitch.tv/yocto_project)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.0.1 was released.
*YP 4.0.35 is due to release
*YP 3.1 M1 rc8 is in QA
*YP 5.3.4 is in QA
*YP 3.1 M1 took a record number of build attempts due to various issues which only appeared during the rc builds.
*YP 6.0 rc1 is in QA
*Despite a successful rc8 build (which still had reproducible build test failures) there are a number of concerns, particularly as there appears to be very slow builds for some ‘pathological’ hashequiv scenarios. There has been some progress over the weekend on identifying the causes of that and partially addressing them.
*There will be no patch review on Monday 4th May due to public holidays.
*There remains a growing set of intermittent autobuilder failures which occur with varying frequencies. We’re struggling to find anyone with time/interest to resolve these and they are becoming problematic for reviewing/testing patches and  triaging builds.
*We continue to triage the CVEs being reported by the new tooling.
*The TSC is working on LTS plans, productive discussions have been had and a new policy on handling this and stable releases should be available in the coming weeks.
*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
*We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
*There have been several issues in pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1 to pull these in.
*Due to holidays in EU/US, the next status report will be sent in early January (likely 7th). If there is anything critical to report this will happen as needed.
*There have been issues with 403 errors from crates.io, there is a change in bitbake to use the preferred upstream urls via their CDN.
*The kvm cpu features issue looks to be a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.
*git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback but are trying to clear the backlog.


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.1 M1 is in QA
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*YP 3.1 M1 release date 12/13/2019
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*YP 3.1 M2 build date 1/20/2020
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*YP 3.1 M2 release date 1/31/2020
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*YP 3.1 M3 build date 2/24/2020
*YP 3.1 M3 release date 3/6/2020
*YP 3.1 M4 build date  3/30/2020
*YP 3.1 M4 release date  4/24/2020


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.7.3 build date  2/10/20
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 2.7.3 release date 2/21/20
*YP 3.0.2 build date  2/3/20
*YP 3.0.2 release date 2/14/20


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2718 (last week 2698) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2788 (last week 2790) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1410 (last week 1410)
**Total patches found: 1085 (last week 1078)
**Patches in the Pending State: 564 (40%) [last week 564 (40%)]
**Patches in the Pending State: 146 (13%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming dot releases:'''<br/>
*YP 4.0.35 is in review.
*YP 5.3.4 is in QA
**Release Date 2026-05-06
*YP 5.0.18
**Build Date  2026-05-11
**Release Date 2026-05-25
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


'''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 45: Line 52:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]

Latest revision as of 14:51, 28 April 2026

Yocto Project Status 28 April 2026

Current Dev Position: YP 6.0 M4
Next Deadline: YP 6.0 Release Date w/c 2026-05-04

Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 4.0.35 is due to release
  • YP 5.3.4 is in QA
  • YP 6.0 rc1 is in QA
  • There will be no patch review on Monday 4th May due to public holidays.
  • We continue to triage the CVEs being reported by the new tooling.
  • There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
  • There have been several issues in pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1 to pull these in.
  • There have been issues with 403 errors from crates.io, there is a change in bitbake to use the preferred upstream urls via their CDN.
  • The kvm cpu features issue looks to be a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.
  • git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
  • We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback but are trying to clear the backlog.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming dot releases:

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=86818"