Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(374 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Nov. 2nd, 2021 ==
== Yocto Project Status 28 April 2026 ==
Current Dev Position: YP 3.5 M1<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: 6th Dec. 2021 YP 3.5 M1 build<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 Nov. 4th at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 30th Apr. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Nov. 2nd at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 29th Apr. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Nov. 9th at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 30th Apr. 10am GMT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.4 has been released. Thanks to everyone who contributed!
*YP 4.0.35 is due to release
*YP 3.3.4 is due to build this week and will be the last planned release of the hardknott series.
*YP 5.3.4 is in QA
*YP 3.5 Planning document: https://docs.google.com/document/d/1OXw-NKoL_Vb9RWI6sRPs3zTcAn4hHPtG0Y2BIs7xIzo/edit?usp=sharing
*YP 6.0 rc1 is in QA
*Git’s default branch choice could potentially change in the future and we’re seeing service providers like github change policy too. To react to this variability the project really needs to start encoding the branch name used in SRC_URI rather than having a default of master. OE-Core has been converted and there is a script ( scripts/contrib/convert-srcuri.py) to help with conversions. Bitbake will start warning where this is unset soon (patch in master-next).
*There will be no patch review on Monday 4th May due to public holidays.
*Github has announced that git protocol support will be dropped as of January. We use this in a number of our SRC_URIs. This has been discussed on the architecture list and we have a plan to warn (and later error) on problematic urls and magically map to the correct urls within bitbake. The latter change is easily backported to older bitbake releases and will allow older branches to continue to function without invasive changes. The conversion script mentioned above can also convert github urls.
*We continue to triage the CVEs being reported by the new tooling.
*We have seen a drop in the number of patches in “Pending” state, partly thanks to work from Richard to send libtool and gcc patches upstream or otherwise clean them up. Others are also stepping forward to try and reduce the number of patches in Pending state, help would be much appreciated as spread over a number of people this could be quickly handled and reduced.
*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
*Intermittent issues continue to rise and help is very much welcome on these 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
*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:'''<br/>
'''Ways to contribute:'''<br/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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=---
*There are bugs that are currently unassigned for YP 3.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhancements.2FBugs
*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/
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing


'''YP 3.5 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 3.5 M1 build date 2021/12/06
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 3.5 M1 Release date 2021/12/17
 
*YP 3.5 M2 build date 2022/01/10
'''Tracking Metrics:'''<br/>
*YP 3.5 M2 Release date 2022/1/21
*WDD 2788 (last week 2790) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.5 M3 build date 2022/2/21
*OE-Core/Poky Patch Metrics
*YP 3.5 M3 Release date 2022/03/04
**Total patches found: 1085 (last week 1078)
*YP 3.5 M4 build date 2022/04/04
**Patches in the Pending State: 146 (13%) [last week 147 (14%)]
*YP 3.5 M4 Release date 2022/04/29
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.3.4 build date 2021/11/01
*YP 4.0.35 is in review.
*YP 3.3.4 Release date 2021/11/12
*YP 5.3.4 is in QA
*YP 3.1.12 build date 2021/11/15
**Release Date 2026-05-06
*YP 3.1.12 Release date 2021/11/26
*YP 5.0.18
*YP 3.4.1 build date 2021/11/22
**Build Date  2026-05-11
*YP 3.4.1 Release date 2021/12/03
**Release Date 2026-05-25
*YP 3.1.13 build date 2021/12/13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 3.1.13 Release date 2021/12/22
*YP 3.1.14 build date 2022/01/24
*YP 3.1.14 Release date 2022/02/04
*YP 3.4.2 build date 2022/02/07
*YP 3.4.2 Release date 2022/02/18
*YP 3.1.15 build date 2022/03/14
*YP 3.1.15 Release date 2022/03/25
*YP 3.4.3 build date 2022/03/21
*YP 3.4.3 Release date 2022/04/01
*YP 3.1.16 build date 2022/04/25
*YP 3.1.16 Release date 2022/05/06
 
'''Tracking Metrics:'''<br/>
*WDD 2655 (last week 2655) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics 
**Total patches found: 1283 (last week 1288)
**Patches in the Pending State: 463 (36%) [last week 476 (37%)]


'''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 63: 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]]
*[[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"