Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(194 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status May 23rd, 2023 ==
== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 4.3 M1<br/>
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: 5th June 2023 YP 4.3 M1 build date<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 May 25th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday May 23rd 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.10 is ready to release after TSC review
* YP 5.0.15 was released
*YP 4.2.1 is in QA
* YP 5.3.1 is under review
*M1 is approaching fast (two weeks left), so please try and get any major changes submitted soon.
* YP 6.0 M1 is in QA
*Patches have been merging into master, thanks to everyone for both review feedback and iterating on patches
* YP 4.0.33 is queued for QA after 6.0 M1
*We need to upgrade to gcc 13 soon, this is blocking enabling Fedora 38 workers on the autobuilder as we don’t have a compatible uninative release.
* YP 6.0 M2 is due next week!
*There are time64 patches being proposed to handle Y2038 issues on 32 bit architectures which likely need further discussion since the compiler flag changes aren’t without risk and potential side effects.
* 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.
*We’re aiming to improve documentation as we go along in this release, please keep this in mind when sending patches. Adding to the documentation as we go will make the release a lot easier.
* There are currently 6 high open bugs, which will block M2:
*Autobuilder instability is a concern as known good builds are regularly hitting issues, particularly the “ubuntu 20.04 libgcc not found” issue which is likely python version specific but there are other intermittent issues too. As an example, three of the last nightly builds failed in succession. Due to the intermittent nature of these bugs, few people are willing to spend time on them but they mean patches are being very slow to merge. Help is very much needed but it is hard to be specific about where/what the issue is unfortunately.
** 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/>
*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
'''New to the project?'''<br/>
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*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 6.0 Milestone Dates:'''<br/>
*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


'''YP 4.3 Milestone Dates:'''<br/>
*YP 4.3 M1 build date  2023/06/05
*YP 4.3 M1 Release date 2023/06/16
*YP 4.3 M2 build date  2023/07/17
*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.10 is ready for release
*YP 5.3.1 is under review.
*YP 4.2.1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 4.2.1 Release date 2023/06/02
*YP 5.0.16 Build Date 2026-02-09
*YP 3.1.26 build date 2023/06/19
*YP 5.0.16 Release Date 2026-02-20
*YP 3.1.26 Release date 2023/06/30
*YP 5.3.2 Build Date 2026-02-16
*YP 4.0.11 build date 2023/06/26
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.11 Release date 2023/07/07
*YP 4.0.34 Build Date 2026-02-23
*YP 4.2.2 build date 2023/07/10
*YP 4.0.34 Release Date 2026-03-06
*YP 4.2.2 Release date 2023/07/21
*YP 5.3.3 Build Date 2026-03-09
*YP 3.1.27 build date 2023/07/31
*YP 5.3.3 Release Date 2026-03-20
*YP 3.1.27 Release date 2023/08/11
*YP 5.0.17 Build Date 2026-03-16
*YP 4.0.12 build date 2023/08/07
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.12 Release date 2023/08/18
*YP 4.0.35 Build Date 2026-04-06
*YP 4.2.3 build date 2023/08/28
*YP 4.0.35 Release Date 2026-04-17
*YP 4.2.3 Release date 2023/09/08
*YP 5.3.4 Build Date 2026-04-13
*YP 3.1.28 build date 2023/09/18
*YP 5.3.4 Release Date 2026-04-24
*YP 3.1.28 Release date 2023/09/29
*YP 5.0.18 Build Date 2026-04-20
*YP 4.0.13 build date 2023/09/25
*YP 5.0.18 Release Date 2026-05-01
*YP 4.0.13 Release date 2023/10/06
*YP 5.0.19 Build Date 2026-05-26
*YP 3.1.29 build date 2023/10/30
*YP 5.0.19 Release Date 2026-06-05
*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 2527 (last week 2535) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1198 (last week 1198)
**Patches in the Pending State: 278 (23%) [last week 278 (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 79: 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"