Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(632 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 9, 2019 ==
== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 2.7 M4 (New feature Freeze has begun.)<br/>
Current Dev Position: YP 6.0 M2<br/>
Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019 and it should release today<br/>
Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
 
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*SWAT lead is currently: Amanda
*Weekly Project Engineering Sync  - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*SWAT team rotation: Amanda -> Chen on Apr. 12, 2019
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*SWAT team rotation: Chen -> Armin on Apr. 19, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*YP 2.8 Planning meeting Tuesday April 2nd at 8am PDT (https://zoom.us/j/990892712)
*Bug Triage meeting Thursday April 4th at 7:30am PDT (https://zoom.us/j/454367603)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.7 M3 rc1 will be released today. The YP 2.7 M3 rc1 report is summarized at https://lists.yoctoproject.org/pipermail/yocto/2019-April/044667.html and the results are at https://autobuilder.yocto.io/pub/releases/yocto-2.7_M3.rc1/testresults/.
*YP 4.0.33 is awaiting approval
*YP 2.5.3 and YP 2.6.2 stable releases were built and have been submitted to QA
*YP 5.0.16 is in QA
*YP 2.6.2 is currently going through the QA process with YP 2.5.3 queued behind it.  
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*Process issues in the way ptest was being processed by QA have been discovered which mean the previous ptest results are not comparable with the new QA process. For consistency going forward we will be using the new QA process as the definitive results and will be comparing for regressions based upon these.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
*The “warrior” branches for 2.7 have been created and the metadata updated, patches are being slowed in line with release stablisation with increasingly critical fixes only.
**rust do_test_compile/do_install segfault (#16058)
*The remaining things which are planned for YP 2.7 M4 before we have the final 2.7 rc1 build are:
**Generation of releases.json needs updating (#16138)
**Upgrading -tiny to the 5.0 linux-yocto kernel (currently 4.18)
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
**Removal of the 4.18 kernel
*Two are currently needing further work:
**Fixing the python3 ptest timeout and result status issues
**x86 kvm broken on Fedora 43 (#16074)
**Fixing some of the util-linux ptest failures
**AB-INT: opkg-build segmentation fault (#16078)
**Potentially integrating a key and long time puzzling pseudo issue
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
**Integrating qemumips shutdown issues identified in the kernel
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
**Continue to investigate python3 testsuite hang on 5.0+ kernels (trying to get help upstream)
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*Worrying things which we don’t have good plans for currently (mainly lack of people to help with):
*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.
**Intermittent autobuilder failures (fork running out of resources - which resources?, oe-selftest intermittent issues, gpg signing resource problems, occasional PR server failure and more)
*Patch review is now using two branches:
**Build-appliance testing issues (show up on each QA report across multiple releases)
**“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)
**40% valgrind ptest failures
**“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)
**Known bitbake memory resident bugs
*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.
**Other ptest failures
*The 2.8 planning discussions are starting and there is a google doc summarising the discussions so far: https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/
*If people are planning to work on specific things in 2.8 please let us know so we can incorporate this into our plans. If you’re interested in working on anything in the document, please also let us know or talk with us in one of the planning meetings.


'''Planned Releases for YP 2.7:'''<br/>
'''Ways to contribute:'''<br/>
*YP 2.7 M4 Cutoff was Apr. 1, 2019
*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=---
*YP 2.7 M4 Release Target is Apr. 26, 2019
*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


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.5.3 (Sumo) is 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 2.6.2 (Thud) is in QA.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2442 (last week 2418) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1542 (last week 1538)
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 654 (42%) [last week 656 (42%)]
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Key Status Links for YP:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status<br/>
*YP 6.0 M2 Build Date 2026-02-16
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule<br/>
*YP 6.0 M2 Release Date 2026-02-27
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features<br/>
*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:'''<br/>
*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/>
https://wiki.yoctoproject.org/wiki/TSC<br/>


== 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]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2019 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"