Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(560 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status May 12, 2020 ==
== Yocto Project Status 28 April 2026 ==
Current Dev Position: YP 3.2 M1 <br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 3.2 M1 build date 2020/6/16<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 May 14th 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 June 2nd 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 May 12th 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 - See http://www.twitch.tv/letoatreidesthe2nd
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*Patches continue to merge into master, there have been a number of infrastructure issues and build failures which have delayed some patches until we could get clean builds
*YP 4.0.35 is due to release
*We’re nearly ready to merge gcc 10 to master with some mingw issues being the currently known remaining blocker.
*YP 5.3.4 is in QA
*A number of other slightly more invasive changes are merging such as the changing of QA warnings to become errors and changes to the way libva is built. Some further, more invasive changes are in the queue (e.g. image sstate structure) so review of the patch queue by people with interests in these things is appreciated.
*YP 6.0 rc1 is in QA
*We believe autoconf may release a new version soon (the first in a few years) so have worked with autoconf upstream to ensure it should work for us, reporting test results back.
*There will be no patch review on Monday 4th May due to public holidays.
*YP 3.0.3 will build this week.
*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.


'''YP 3.2 Milestone Dates:'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.2 M1 build date 2020/6/16
*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.2 M1 Release date 2020/6/26
*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.2 M2 build date 2020/7/27
*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.2 M2 Release date 2020/8/7
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*YP 3.2 M3 build date 2020/8/31
*YP 3.2 M3 Release date 2020/9/11
*YP 3.2 M4 build date 2020/10/5
*YP 3.2 M4 Release date 2020/10/30


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 3.0.3 build date 2020/5/4
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 3.0.3 release date 2020/5/15
*YP 2.7.4 build date 2020/5/18
*YP 2.7.4 release date 2020/5/29
*YP 3.1.1 build date 2020/6/29
*YP 3.1.1 release date 2020/7/10
*YP 3.0.4 build date 2020/8/10
*YP 3.0.4 release date 2020/8/21
*YP 3.1.2 build date 2020/9/14
*YP 3.1.2 release date 2020/9/25


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2577 (last week 2577) (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: 1345 (last week 1353)
**Total patches found: 1085 (last week 1078)
**Patches in the Pending State: 536 (40%) [last week 536 (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 48: 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"