Re: [OE-core] Yocto Project Status WW08`22

Anuj Mittal

On Sun, 2022-02-27 at 07:28 -0800, Armin Kuster wrote:
I see there is an April release of Hardknott.  Is that the last
Hardknott release from the Yocto Project?
There's going to be a 3.3.6 as well and that is going to be the last.
From this status email:

* YP 3.3.6 build date 2022/03/28
* YP 3.3.6 Release date 2022/04/08




On 2/22/22 07:54, Stephen Jolley wrote:

Current Dev Position: YP 3.5 M4

Next Deadline: 4th April. 2022 YP 3.5 M4 build

Next Team Meetings:

  * Bug Triage meeting Thursday Feb. 24th 7:30 am PDT
  * Monthly Project Meeting Tuesday Mar. 1st at 8 am PDT
  * Weekly Engineering Sync Tuesday Feb. 22nd at 8 am PDT
  * Twitch - See

Key Status/Updates:

  * We are now at feature freeze for 3.5, our next LTS release
  * YP 3.1.14 and YP 3.2.4 were released
  * YP 3.3.5 is in QA
  * After a last minute push, the base set of inclusive language
    changes have merged. There is a conversion script which can be
    to convert layers. Not all changes needed have been written yet
    but enough are present to allow the conversion process to
  * There were also changes to convert LICENSE fields to use SPDX
    identifiers and there is a second conversion script for this
    can be used.
  * We have updated the core layer series name to kirkstone and
    layers will now need to update to confirm compatibility with
  * There is a patchset to update python’s build processes to use
    upstream preferred wheel approach which would aid support of
    python over the next few years. It is late in the cycle for
    kind of change but we will give this series a few days of
    to make a decision and welcome user feedback either way on
  * As such, the M3 release build will likely not happen until
    next week.
  * The autobuilder infrastructure is planned to be offline 26-28th
    February for a data center move. Public services like the
    wiki and git servers will remain live but the git backend
    ( will be offline, as will the downloads
    sstate services and the autobuilder/NAS.
  * Capacity has been improved on the sstate server which was
    intermittent timeout issues for downloads.
  * Intermittent issues continue to be at record high levels and
    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:

In particular, we’re struggling to understand the intermittent
issue with external hosts we’re seeing very occasionally.

Ways to contribute:

  * There are bugs identified as possible for newcomers to the
  * There are bugs that are currently unassigned for YP 3.5. See:
  * We’d welcome new maintainers for recipes in OE-Core. Please see
    the list at:
    and discuss with the existing maintainer, or ask on the OE-Core
    mailing list. We will likely move a chunk of these to
    soon to help facilitate this.
  * Help us resolve CVE issues: CVE metrics

YP 3.5 Milestone Dates:

  * YP 3.5 M3 build date 2022/02/21
  * YP 3.5 M3 Release date 2022/03/04
  * YP 3.5 M4 build date 2022/04/04
  * YP 3.5 M4 Release date 2022/04/29

Upcoming dot releases:

  * YP 3.1.14  is released
  * YP 3.4.2 is released
  * YP 3.3.5 is in QA
  * YP 3.3.5 Release date 2022/02/25
  * YP 3.1.15 build date 2022/03/14
  * YP 3.1.15 Release date 2022/03/25
  * YP 3.4.3 build date 2022/03/21
  * YP 3.4.3 Release date 2022/04/01
  * YP 3.3.6 build date 2022/03/28
  * YP 3.3.6 Release date 2022/04/08
  * YP 3.1.16 build date 2022/04/25
  * YP 3.1.16 Release date 2022/05/06

Tracking Metrics:

  * WDD 2652 (last week
  * OE-Core/Poky Patch Metrics
      o Total patches found: 1202 (last week 1208)
      o Patches in the Pending State: 334 (28%) [last week 334

The Yocto Project’s technical governance is through its Technical
Steering Committee, more information is available at: 

The Status reports are now stored on the wiki at: 

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


*/Stephen K. Jolley/**//*

*Yocto Project Program Manager*

(*Cell*: (208) 244-4460

* *Email*

Join { to automatically receive all group messages.