Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(398 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 13, 2021 ==
== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 3.4 M2<br/>
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: 12th July 2021 YP 3.4 M2 build<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-02<br/>
6
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday July 15th at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday July 13th at 8am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday July 20th at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1.9 was released.
* YP 5.0.15 was released
*The prserv rewrite is still pending on resolving the issues with python asyncio.
* YP 5.3.1 is under review
*Alexandre Belloni/Bootlin have been taking over some of the patch testing/queuing work over the last couple of weeks, feedback to either Richard/Alexandre or the TSC on how this is working is welcome.
* YP 6.0 M1 is in QA
*Intermittent autobuilder issues continue to occur, about 50% of the open issues are now ptest failures, many occurring more frequently on arm and the rest are various other races or timeouts. 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
* YP 4.0.33 is queued for QA after 6.0 M1
*We have made progress on a couple of the race issues and on one of the ptest issues (util-linux), some of the ptest issues and the bitbake server timeout issue are now our most frequently encountered issues.
* YP 6.0 M2 is due next week!
*A rootfs license race issue (#14123) now has reproduction steps which should allow a fix to follow.
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
*The multiconfig changes in bitbake continue to cause problems, we still need simpler test cases to reproduce issues rather than huge builds. The existing patches seem to fix some workloads and break others and current test cases are very slow to work with.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
 


'''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
 
'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
 
'''Tracking Metrics:'''<br/>
* WDD 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 


'''YP 3.4 Milestone Dates:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 3.4 M2 build date 2021/07/12
*YP 6.0 M2 Build Date 2026-02-02
*YP 3.4 M2 Release date 2021/07/23
*YP 6.0 M2 Release Date 2026-02-13
*YP 3.4 M3 build date 2021/08/23
*YP 6.0 M3 Build Date 2026-03-02
*YP 3.4 M3 Release date 2021/09/03
*YP 6.0 M3 Release Date 2026-03-13
*YP 3.4 M4 build date 2021/10/04
*YP 6.0 M4 Build Date 2026-03-30
*YP 3.4 M4 Release date 2021/10/29
*YP 6.0 M4 Release Date 2026-04-26


'''Planned upcoming dot releases:'''<br/>
*YP 3.3.2 build date 2021/07/19
*YP 3.3.2 release date 2021/07/30
*YP 3.1.10 build date 2021/07/26
*YP 3.1.10 release date 2021/08/06
*YP 3.1.11 build date 2021/09/13
*YP 3.1.11 release date 2021/9/24


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2658 (last week 2668) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.3.1 is under review.
*Poky Patch Metrics 
*YP 4.0.33 is queued for QA after 6.0 M1.
**Total patches found: 1284 (last week 1276)
*YP 5.0.16 Build Date 2026-02-09
**Patches in the Pending State: 480 (37%) [last week 481 (38%)]
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05


'''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 49: Line 79:


== 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:24, 27 January 2026

Yocto Project Weekly Status Jan. 27th, 2026

Current Dev Position: YP 6.0 M1
Next Deadline: YP 6.0 M2 Build Date 2026-02-02
6 Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.15 was released
  • YP 5.3.1 is under review
  • YP 6.0 M1 is in QA
  • YP 4.0.33 is queued for QA after 6.0 M1
  • YP 6.0 M2 is due next week!
  • Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
  • There are currently 6 high open bugs, which will block M2:
    • Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
    • x86 kvm broken on Fedora 43 (#16074)
    • AB-INT: build-sysroots: useradd command did not succeed (#16135)
    • Hangs of the autobuilder controller (database locking?) (#16129)
    • Generation of releases.json needs updating (#16138)
  • The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
  • Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.


Ways to contribute:

New to the project?

Tracking Metrics:


YP 6.0 Milestone Dates:

  • YP 6.0 M2 Build Date 2026-02-02
  • YP 6.0 M2 Release Date 2026-02-13
  • YP 6.0 M3 Build Date 2026-03-02
  • YP 6.0 M3 Release Date 2026-03-13
  • YP 6.0 M4 Build Date 2026-03-30
  • YP 6.0 M4 Release Date 2026-04-26


Upcoming dot releases:

  • YP 5.3.1 is under review.
  • YP 4.0.33 is queued for QA after 6.0 M1.
  • YP 5.0.16 Build Date 2026-02-09
  • YP 5.0.16 Release Date 2026-02-20
  • YP 5.3.2 Build Date 2026-02-16
  • YP 5.3.2 Release Date 2026-02-27
  • YP 4.0.34 Build Date 2026-02-23
  • YP 4.0.34 Release Date 2026-03-06
  • YP 5.3.3 Build Date 2026-03-09
  • YP 5.3.3 Release Date 2026-03-20
  • YP 5.0.17 Build Date 2026-03-16
  • YP 5.0.17 Release Date 2026-03-23
  • YP 4.0.35 Build Date 2026-04-06
  • YP 4.0.35 Release Date 2026-04-17
  • YP 5.3.4 Build Date 2026-04-13
  • YP 5.3.4 Release Date 2026-04-24
  • YP 5.0.18 Build Date 2026-04-20
  • YP 5.0.18 Release Date 2026-05-01
  • YP 5.0.19 Build Date 2026-05-26
  • YP 5.0.19 Release Date 2026-06-05

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