Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
Line 1: Line 1:
== Yocto Project Status 15 September 2026 ==
== Yocto Project Status 22 September 2026 ==
Current Dev Position: YP 6.1 M4 - Stabilization (Bug Fixing)<br/>
Current Dev Position: YP 6.1 M4 - Stabilization (Bug Fixing)<br/>
Next Deadline: YP 6.1 M4: w/c 2026-10-12<br/>
Next Deadline: YP 6.1 M4: w/c 2026-10-12<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 17th Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 24th Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 15th Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 22nd Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 17th Sept. 10am GMT and Monday 21st Sept. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 24th Sept. 10am GMT and Monday 28th Sept. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.0.20 is due for release
*YP 5.0.20 was released
*YP 6.1 M3 is in QA
*YP 6.1 M3 is due for release
*We have removed much of the github.com usage in bitbake-selftest which is improving autobuilder connectivity issues. Some references remain, see the link below.
*Our plan is to build M4 within the next week unless significant problems become known as we’re not aware of anyone working on any major fixes which would delay it.
*There is a possibility that openssl 4.0 is causing TLS issues in git connection requests in CI. Help/insight welcome.
*If there are release blocking issues, please report ASAP.
*There is a vblank kernel warning message causing problems in CI with the 7.2 kernel.
*We have made progress on the build architecture reproducibility issues, thanks in particular to Alejandro and Sunil and team at Windriver for getting the major rust issues resolved. There are around 30 issues left as shown by the *autobuilder tests (down from ~90) so great progress.
*Given the limited number of people working on bug fixing, the number of issues likely to be fixed in M4 is low and we are considering speeding up M4 by a few weeks, allowing more time for 6.2 M1 and for the release to be built by ELC in Prague.
*python3-six recipe moved to meta-oe, it provides python 2.x era support so nothing should be needing that now - references are a sign that dependencies probably need updating but it is still available if needed.
*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
*Adrian has made significant improvements to the IDE integration with devtool which have now merged, thanks!
*There are issues which are in a position where others could now help:
*There are issues which are in a position where others could now help:
**Matchbox-wm segfault/xserver restart
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue - thanks for the work and fixes so far on this.
**aarch64/x86-64 build host contamination/reproducibility issue - thanks for the work and fixes so far on this.
    See Richard’s email on the list https://lists.openembedded.org/g/openembedded-core/topic/areas_we_could_do_with/121159956 which details some others too
**See Richard’s email on the list https://lists.openembedded.org/g/openembedded-core/topic/areas_we_could_do_with/121159956 which details some others too
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.


Line 35: Line 33:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2647 (last week 2622) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2640 (last week 2647) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1054 (last week 1050)
**Total patches found: 1055 (last week 1054)
**Patches in the Pending State: 135 (13%) [last week 136 (1%)]
**Patches in the Pending State: 137 (13%) [last week 135 (1%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3


'''Upcoming development releases:'''<br/>
'''Upcoming development releases:'''<br/>
*6.1 M3: is in QA.
*6.1 M3: is due for release
**Release Date: w/c 2026-09-14
*6.1.0:
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Build Date (M4): w/c 2026-10-12
Line 49: Line 46:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.20 is due for release.
*YP 5.0.20 was released
**Release Date w/c 2026-08-31
*YP 6.0.4
*YP 6.0.4
**Build Date w/c 2026-09-28
**Build Date w/c 2026-09-28

Latest revision as of 14:45, 22 September 2026

Yocto Project Status 22 September 2026

Current Dev Position: YP 6.1 M4 - Stabilization (Bug Fixing)
Next Deadline: YP 6.1 M4: w/c 2026-10-12

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.20 was released
  • YP 6.1 M3 is due for release
  • Our plan is to build M4 within the next week unless significant problems become known as we’re not aware of anyone working on any major fixes which would delay it.
  • If there are release blocking issues, please report ASAP.
  • We have made progress on the build architecture reproducibility issues, thanks in particular to Alejandro and Sunil and team at Windriver for getting the major rust issues resolved. There are around 30 issues left as shown by the *autobuilder tests (down from ~90) so great progress.
  • python3-six recipe moved to meta-oe, it provides python 2.x era support so nothing should be needing that now - references are a sign that dependencies probably need updating but it is still available if needed.
  • There are issues which are in a position where others could now help:

We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M3: is due for release
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 5.0.20 was released
  • YP 6.0.4
    • Build Date w/c 2026-09-28
    • Release Date w/c 2026-10-12
  • YP 5.0.21
    • Build Date w/c 2026-10-05
    • Release Date w/c 2026-10-19

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