Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(152 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status November 21st, 2023 ==
== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 5.0 M1<br/>
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: 4th December 2023 YP 5.0 M1 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)


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday November 23, 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday November 21st at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester
<br/>
'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.14 and YP 3.1.29 were released
* YP 5.0.15 was released
*YP 4.2.4  has passed QA and under discussion pending release
* YP 5.3.1 is under review
*Toaster news:
* YP 6.0 M1 is in QA
**Testing for toaster is now starting to be enabled on the autobuilder although not all tests are currently passing and there are host specific issues.
* YP 4.0.33 is queued for QA after 6.0 M1
**The ability to view existing builds is being extended to allow debugging use of toaster even if the original build didn’t use it
* YP 6.0 M2 is due next week!
*In support of the above, BB_DEFAULT_EVENTLOG is being proposed as enabled by default in bitbake.conf so that an event log is stored for all builds. This could be useful for debugging outside of toaster in other tools too. There is a small performance/disk footprint overhead but this should be offset by the useful debug data.
* 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 length of builds (world and oe-selftest) continues to be a concern.
* There are currently 6 high open bugs, which will block M2:
*When running the first nanbield stable series builds, our LTS maintainer remarked on being unable to get successful green builds. We did make significant improvements on the intermittent issues prior to release but clearly not enough unfortunately. Troubling issues include:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15005 - parsing failure on ubuntu2004/debian11 systems, maybe python/pthreads related with host python
** x86 kvm broken on Fedora 43 (#16074)
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15166 - debuginfod issues (Ross has some debugging improvements pending)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
**Devtool “initial_rev” race issue, an example failure: https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/6082/steps/14/logs/stdio
** Hangs of the autobuilder controller (database locking?) (#16129)
**several intermittent pstest issues
** Generation of releases.json needs updating (#16138)
*There have been several fixes for meta-openembedded reproducibility issues and fixes for mirroring/CVE reporting on stable release branches, thanks Yoann.
* 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.




<br/>
'''Ways to contribute:'''<br/>
*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 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/
*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


'''Ways to contribute:'''<br/>
'''New to the project?'''<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 a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs that are currently unassigned for YP 4.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_Unassigned_Enhancements.2FBugs
*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.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''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 5.0 Milestone Dates:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 5.0 M1 build date 2023/12/04
*YP 6.0 M2 Build Date 2026-02-02
*YP 5.0 M1 Release date 2023/12/15
*YP 6.0 M2 Release Date 2026-02-13
*YP 5.0 M2 build date  2024/01/15
*YP 6.0 M3 Build Date 2026-03-02
*YP 5.0 M2 Release date 2024/01/24
*YP 6.0 M3 Release Date 2026-03-13
*YP 5.0 M3 build date  2024/02/19
*YP 6.0 M4 Build Date 2026-03-30
*YP 5.0 M3 Release date 2024/03/01
*YP 6.0 M4 Release Date 2026-04-26
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30




'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.29 build date 2023/10/30
*YP 5.3.1 is under review.
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 4.0.14 build date 2023/11/06
*YP 5.0.16 Build Date 2026-02-09
*YP 4.0.14 Release date 2023/11/17
*YP 5.0.16 Release Date 2026-02-20
*YP 4.2.4 build date 2023/11/13
*YP 5.3.2 Build Date 2026-02-16
*YP 4.2.4 Release date 2023/11/24
*YP 5.3.2 Release Date 2026-02-27
*YP 4.3.1 build date 2023/11/27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.3.1 Release date 2023/12/08
*YP 4.0.34 Release Date 2026-03-06
*YP 3.1.30 build date 2023/12/11
*YP 5.3.3 Build Date 2026-03-09
*YP 3.1.30 Release date 2023/12/22
*YP 5.3.3 Release Date 2026-03-20
*YP 4.0.15 build date 2023/12/18
*YP 5.0.17 Build Date 2026-03-16
*YP 4.0.15 Release date 2023/12/29
*YP 5.0.17 Release Date 2026-03-23
*YP 4.3.2 build date 2024/01/08
*YP 4.0.35 Build Date 2026-04-06
*YP 4.3.2 Release date 2024/01/19
*YP 4.0.35 Release Date 2026-04-17
*YP 3.1.31 build date 2024/01/22
*YP 5.3.4 Build Date 2026-04-13
*YP 3.1.31 Release date 2024/02/02
*YP 5.3.4 Release Date 2026-04-24
*YP 4.0.16 build date 2024/01/29
*YP 5.0.18 Build Date 2026-04-20
*YP 4.0.16 Release date 2024/02/09
*YP 5.0.18 Release Date 2026-05-01
*YP 4.3.3 build date 2024/02/12
*YP 5.0.19 Build Date 2026-05-26
*YP 4.3.3 Release date 2024/02/23
*YP 5.0.19 Release Date 2026-06-05
*YP 3.1.32 build date 2024/03/04
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.17 build date 2024/03/11
*YP 4.0.17 Release date 2024/03/22
*YP 4.3.4 build date 2024/03/25
*YP 4.3.4 Release date 2024/04/05
*YP 3.1.33 build date 2024/04/15
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.18 build date 2024/04/22
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.19 build date 2024/06/03
*YP 4.0.19 Release date 2024/06/14
 
 
'''Tracking Metrics:'''<br/>
*WDD 2517 (last week 2533) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1177 (last week 1177)
**Patches in the Pending State: 253 (21%) [last week 253 (21%)]
*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 96: 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]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 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"