Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(224 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 11th, 2023 ==
== Yocto Project Status 28 April 2026 ==
Current Dev Position: YP 4.2 M4<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: 28th April 2023 YP 4.2 Release<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 April13h 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 30th Apr. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday April 11th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 29th Apr. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 30th Apr. 10am GMT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.2 rc2 is now in QA
*YP 4.0.35 is due to release
*YP 4.0.9 is being built
*YP 5.3.4 is in QA
*Due to some concerns about crate urls, 4.2 rc1 was abandoned and rc2 built.
*YP 6.0 rc1 is in QA
*linux-yocto is no longer excluded from CVE reporting on master, thanks to all who have helped triage the CVE list for the kernel. https://autobuilder.yocto.io/pub/non-release/patchmetrics/cve-status-master.txt
*There will be no patch review on Monday 4th May due to public holidays.
*We’re happy to announce that Steve Sakoman is going to be supporting the mickledore stable series.
*We continue to triage the CVEs being reported by the new tooling.
*The langdale release series will now wind down after one final point release
*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
*Patches should soon start flowing into master for 4.3
*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.
*The project is looking at a funding opportunity where projects with a specific development focus may be able to be funded. Ideas coming to mind might include bringing back patchtest or toaster’s automated testing. If anyone has ideas that we’d be able to find people to work on (contract based?) within a reasonable timeframe, we’d be interested to hear the things people feel would make the biggest difference to the project.
*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.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*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/>
*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!
*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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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/
*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
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*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 us resolve CVE issues: CVE metrics


'''YP 4.2 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 4.2 M4 built and in QA
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 4.2 M4 Release date 2023/04/28


'''YP 4.3 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.2 M4 build date 2023/04/03
*WDD 2788 (last week 2790) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.2 M4 Release date 2023/04/28
*OE-Core/Poky Patch Metrics
*YP 4.3 M1 build date  2023/06/05
**Total patches found: 1085 (last week 1078)
*YP 4.3 M1 Release date 2023/06/16
**Patches in the Pending State: 146 (13%) [last week 147 (14%)]
*YP 4.3 M2 build date  2023/07/17
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
*YP 4.3 M2 Release date 2023/07/28
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.9 building
*YP 4.0.35 is in review.
*YP 4.0.9 Release date 2023/04/21
*YP 5.3.4 is in QA
*YP 4.1.4 build date 2023/05/01
**Release Date 2026-05-06
*YP 4.1.4 Release date 2023/05/13
*YP 5.0.18
*YP 3.1.25 build date 2023/05/08
**Build Date  2026-05-11
*YP 3.1.25 Release date 2023/05/19
**Release Date 2026-05-25
*YP 4.0.10 build date 2023/05/15
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.0.10 Release date 2023/05/26
*YP 4.2.1 build date 2023/05/22
*YP 4.2.1 Release date 2023/06/02
*YP 3.1.26 build date 2023/06/19
*YP 3.1.26 Release date 2023/06/30
*YP 4.0.11 build date 2023/06/26
*YP 4.0.11 Release date 2023/07/07
*YP 4.2.2 build date 2023/07/10
*YP 4.2.2 Release date 2023/07/21
*YP 3.1.27 build date 2023/07/31
*YP 3.1.27 Release date 2023/08/11
*YP 4.0.12 build date 2023/08/07
*YP 4.0.12 Release date 2023/08/18
*YP 4.2.3 build date 2023/08/28
*YP 4.2.3 Release date 2023/09/08
*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:'''<br/>
*WDD 2531 (last week 2504) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1200 (last week 1195)
**Patches in the Pending State: 278 (23%) [last week 277 (23%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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 92: 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]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 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"