Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(343 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 11th, 2022 ==
== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 3.5 M2<br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: 17th Jan. 2022 YP 3.5 M2 build<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Jan. 13th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Feb. 1st at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Jan. 11th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (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.5 M1 and YP 3.1.13 were released.
*YP 4.0.33 is awaiting approval
*We have two weeks before the 3.5 M2 build.
*YP 5.0.16 is in QA
*The autobuilder has undergone significant changes. There are some not unexpected  issues with the new distros now in use there such as python 3.12 deprecations which trigger warnings on Fedora 35. One of the workers does appear to have what is potentially a hardware issue and not all the workers have migrated to SSDs yet (about 50% so far) so there will be some further disruption as this takes place.
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*On modern kernels, we now have the capability within bitbake to disable networking on a per task basis without extra user privileges. There is discussion on the mailing list on how we should enable this and whether it should be on an opt-in or opt-out basis. There is a proof of concept patchset for the opt-out basis and some good arguments for and against the opt-in approach.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
*The new year triggered some reproducible build failures in openssl and webkit due to changing copyright years in the source files, which is a sign of how detailed our reproducibility tests are.
**rust do_test_compile/do_install segfault (#16058)
*There is a patchset implementing reproducibility for go which is a welcome improvement and much less invasive than previous approaches.
**Generation of releases.json needs updating (#16138)
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review”  - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging 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.5. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_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 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 3.5 Milestone Dates:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 3.5 M2 build date 2022/01/17
*YP 6.0 M2 Build Date 2026-02-16
*YP 3.5 M2 Release date 2022/01/28
*YP 6.0 M2 Release Date 2026-02-27
*YP 3.5 M3 build date 2022/02/21
*YP 6.0 M3 Build Date 2026-03-09
*YP 3.5 M3 Release date 2022/03/04
*YP 6.0 M3 Release Date 2026-03-20
*YP 3.5 M4 build date 2022/04/04
*YP 6.0 M4 Build Date 2026-03-30
*YP 3.5 M4 Release date 2022/04/29
*YP 6.0 M4 Release Date 2026-04-26


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.14 build date 2022/01/24
*YP 5.0.16 Release Date 2026-02-20
*YP 3.1.14 Release date 2022/02/04
*YP 5.3.2 Build Date 2026-02-16
*YP 3.4.2 build date 2022/02/07
*YP 5.3.2 Release Date 2026-02-27
*YP 3.4.2 Release date 2022/02/18
*YP 4.0.34 Build Date 2026-02-23
*YP 3.3.5 build date 2022/02/14
*YP 4.0.34 Release Date 2026-03-06
*YP 3.3.5 Release date 2022/02/25
*YP 5.3.3 Build Date 2026-03-09
*YP 3.1.15 build date 2022/03/14
*YP 5.3.3 Release Date 2026-03-20
*YP 3.1.15 Release date 2022/03/25
*YP 5.0.17 Build Date 2026-03-16
*YP 3.4.3 build date 2022/03/21
*YP 5.0.17 Release Date 2026-03-23
*YP 3.4.3 Release date 2022/04/01
*YP 4.0.35 Build Date 2026-04-06
*YP 3.3.6 build date 2022/03/28
*YP 4.0.35 Release Date 2026-04-17
*YP 3.3.6 Release date 2022/04/08
*YP 5.3.4 Build Date 2026-04-13
*YP 3.1.16 build date 2022/04/25
*YP 5.3.4 Release Date 2026-04-24
*YP 3.1.16 Release date 2022/05/06
*YP 5.0.18 Build Date 2026-04-20
 
*YP 5.0.18 Release Date 2026-05-01
'''Tracking Metrics:'''<br/>
*YP 5.0.19 Build Date 2026-05-26
*WDD 2655 (last week 2653) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.19 Release Date 2026-06-05
*Poky Patch Metrics
**Total patches found: 1234 (last week 1227)
**Patches in the Pending State: 348 (28%) [last week 347 (28%)]


'''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 57: Line 77:


== 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]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]

Latest revision as of 15:56, 17 February 2026

Yocto Project Status 17 February 2026

Current Dev Position: YP 6.0 M2
Next Deadline: YP 6.0 M2 Build Date 2026-02-16

Next Team Meetings:

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

Key Status/Updates:

  • YP 4.0.33 is awaiting approval
  • YP 5.0.16 is in QA
  • YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
  • There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
    • rust do_test_compile/do_install segfault (#16058)
    • Generation of releases.json needs updating (#16138)
    • AB-INT: do_image_wic: tar command return exit status 2 (#16143)
  • Two are currently needing further work:
    • x86 kvm broken on Fedora 43 (#16074)
    • AB-INT: opkg-build segmentation fault (#16078)
  • We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
  • We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
  • We removed legacy tls support from openssl in the interests of providing better secure defaults.
  • The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
  • Patch review is now using two branches:
  • Patches are merging 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-16
  • YP 6.0 M2 Release Date 2026-02-27
  • YP 6.0 M3 Build Date 2026-03-09
  • YP 6.0 M3 Release Date 2026-03-20
  • YP 6.0 M4 Build Date 2026-03-30
  • YP 6.0 M4 Release Date 2026-04-26

Upcoming dot releases:

  • 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=86770"