Yocto Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto@lists.yoctoproject.org,
	openembedded-core@lists.openembedded.org,
	 yocto-status <yocto-status@lists.yoctoproject.org>
Cc: "Stephen K Jolley (via Google Docs)" <sjolley.yp.pm@gmail.com>
Subject: Yocto Project Status 8 September 2026 (WW37)
Date: Tue, 08 Sep 2026 15:45:56 +0100	[thread overview]
Message-ID: <5c0a2b2c6c5d35b57eff6a75ce57a7acf625e34d.camel@linuxfoundation.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 4593 bytes --]

Current Dev Position: YP 6.1 M3 - Feature Freeze
Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:
 * Bug Triage meeting - Thursday 10th Sept. 7:30am PDT
   (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
 * Weekly Project Engineering Sync  - Tuesday 8th Sept. 8am PDT
   (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
   [1]
 * Yocto Project Patch Review - Thursday 10th Sept. 10am GMT and Monday
   14th Sept. 9am PDT
   (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1
   )

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

Key Status/Updates:
 * YP 6.0.3 was released
 * YP 5.0.20 is under review.
 * YP 6.1 M3 is due to build and we are at feature freeze
 * There are issues with changes in bot/AI protection at github.com
   which are affecting our CI. 
 * Most M3 changes have merged, we want to mitigate the github issues
   before building M3.
 * There is a new meta-openjdk layer:
   https://github.com/amarula/meta-openjdk
https://lore.kernel.org/yocto-patches/xBB4.1788187111192557019.ULaN@lists.yoctoproject.org/T/#u
 * 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.
 * There are two AB-INT issues which are in a position where others
   could now help, as detailed in
   https://lists.openembedded.org/g/openembedded-core/message/242105:
    - Matchbox-wm segfault/xserver restart
    - aarch64/x86-64 build host contamination/reproducibility issue
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.
 * Remaining intermittent build failures of concern:
    - other qemu ‘hang’ type issues on ARM
    - sometimes yocto-check-layer is showing checksum mismatch issues
    - intermittent ptest failures in many recipes

Want to contribute? We would appreciate help with the following areas:
 * 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

New to the project?
 * We have a list of issues we think are good places to start
   contributing:
   https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

Tracking Metrics:
 * WDD 2622 (last week 2612)
   (https://wiki.yoctoproject.org/charts/combo.html)
 * OE-Core/Poky Patch Metrics
    - Total patches found: 1050 (last week 1039)
    - Patches in the Pending State: 136 (13%) [last week 139 (14%)]
    - https://valkyrie.yocto.io/pub/non-release/patchmetrics/

Upcoming development releases:
 * 6.1 M3:
    - Build Date: w/c 2026-08-31
    - Release Date: w/c 2026-09-14
 * 6.1.0:
    - Build Date (M4): w/c 2026-10-12
    - Release Date: w/c 2026-11-02

Upcoming dot releases:
 * YP 6.0.3 is in review,
    - Release Date w/c 2026-08-24
 * YP 5.0.20 is in QA.
    - Release Date w/c 2026-08-31
 * 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
 * For future release dates, see
   https://wiki.yoctoproject.org/wiki/Release_calendar

The Yocto Project’s technical governance is through its Technical
Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

The Status reports are stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on
this weekly status update, let us know!]

[1] ) https://zoom.us/j/990892712

[-- Attachment #2: Type: text/html, Size: 51196 bytes --]

                 reply	other threads:[~2026-09-08 14:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5c0a2b2c6c5d35b57eff6a75ce57a7acf625e34d.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sjolley.yp.pm@gmail.com \
    --cc=yocto-status@lists.yoctoproject.org \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox