($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Stephen K Jolley <sjolley.yp.pm@gmail.com>
To: Yocto-mailing-list <yocto@lists.yoctoproject.org>,
	 ",openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status 27 February 2024 (WW09)
Date: Tue, 27 Feb 2024 08:45:56 -0700	[thread overview]
Message-ID: <CAK5yBb8rfYmuTQgy0L2zpH-GcNBc8mLJnCLKPsk-bFqq-A9KLA@mail.gmail.com> (raw)

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

Current Dev Position: YP 5.0 M3 - Feature Freeze

Next Deadline: 19th February 2024 YP 5.0 M3 build

Next Team Meetings:

   -

   Bug Triage meeting Thursday February 29th at 7:30 am PST (
   https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
   -

   Weekly Project Engineering Sync Tuesday February 27th at 8 am PST (
   https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
   <https://zoom.us/j/990892712>
   -

   Twitch -  See https://www.twitch.tv/theyoctojester


Key Status/Updates:

   -

   We are now at feature freeze for 5.0, preparing to build M3
   -

   YP 4.3.3 passed QA and is in review pending release
   -

   The changes which we’d still like to see in 5.0 that have not merged yet
   are:
   -

      genericarm64 machine (there is a draft and it is close)
      -

      QA screenshot comparison
      -

      sstate permissions issue testcase
      -

   Several changes have merged for M3:
   -

      ncurses based task dependency explorer (thanks David!)
      -

      change to rust test suite logging
      -

      useradd fix
      -

      dbus configuration security fix
      -

      bitbake hashserve improvements to better position future server
      capability/functionality
      -

      tweaks to support recipe locale support
      -

      support for BB_LOADFACTOR_MAX
      <https://git.yoctoproject.org/poky/commit/?id=08aa69a1fd7983dcf93d283e47e3c5ac9bd377b1>
      load regulation in bitbake when psi is unavailable.
      -

      further IDE integration tweaks and improvements
      -

   There are also several concerning issues without any clear resolution
   path at present:
   -

      rust upgrade blocked by reproducibility issues
      -

      musl upgrade blocked by large number of unsubmitted pending patches
      -

      nativesdk-systemd usage broken by usrmerge requirement (we can’t
      changing the SDK layout now)
      -

      go isn't upgraded (although there now are partial patches)
      -

   There have been questions about official RISC-V support in this next
   release, especially since it is an LTS. We will trial qemuriscv64 support
   in M3 but remove it before the final LTS release as there is no sponsor for
   that support.


Ways to contribute:

   -

   As people are likely aware, the project has a number of components which
   are either unmaintained, or have people with little to no time trying to
   keep them alive. These components include: devtool, toaster, wic, oeqa,
   autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help
   is welcome in trying to better look after these components!
   -

   There are bugs identified as possible for newcomers to the project:
   https://wiki.yoctoproject.org/wiki/Newcomers
   -

   There are bugs that are currently unassigned for YP 5.0. See:
   https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
   -

   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.
   -

   Help is very much welcome in trying to resolve our autobuilder
   intermittent issues. 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.
   -

   Help us resolve CVE issues: CVE metrics
   <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
   -

   We have a growing number of bugs in bugzilla, any help with them is
   appreciated.
   -

   Regarding bugs, even if you can’t fix a bug, submitting a failing test
   case that can reproduce the issue significantly improves the chances it
   might get fixed.


YP 5.0 Milestone Dates:

   -

   YP 5.0 M3 build date  2024/02/19
   -

   YP 5.0 M3 Release date 2024/03/01
   -

   YP 5.0 M4 build date  2024/04/01
   -

   YP 5.0 M4 Release date 2024/04/30


Upcoming dot releases:

   -

   YP 4.3.3 is ready for release
   -

   YP 3.1.32 build date 2024/03/04
   -

   YP 3.1.32 Release date 2024/03/15
   -

   YP 4.0.17 build date 2024/03/11
   -

   YP 4.0.17 Release date 2024/03/22
   -

   YP 4.3.4 build date 2024/03/25
   -

   YP 4.3.4 Release date 2024/04/05
   -

   YP 3.1.33 build date 2024/04/15
   -

   YP 3.1.33 Release date 2024/04/26
   -

   YP 4.0.18 build date 2024/04/22
   -

   YP 4.0.18 Release date 2024/05/03
   -

   YP 4.0.19 build date 2024/06/03
   -

   YP 4.0.19 Release date 2024/06/14


Tracking Metrics:

   -

   WDD 2633 (last week 2636) (
   https://wiki.yoctoproject.org/charts/combo.html)
   -

   OE-Core/Poky Patch Metrics
   -

      Total patches found: 1144 (last week 1145)
      -

      Patches in the Pending State: 250 (22%) [last week 250 (22%)]
      -

   https://autobuilder.yocto.io/pub/non-release/patchmetrics/


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 now 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!]

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

(    *Cell*:                (208) 244-4460

* *Email*:                 *s
<stephen.k.jolley@intel.com>jolley.yp.pm@gmail.com <jolley.yp.pm@gmail.com>*

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

                 reply	other threads:[~2024-02-27 15: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=CAK5yBb8rfYmuTQgy0L2zpH-GcNBc8mLJnCLKPsk-bFqq-A9KLA@mail.gmail.com \
    --to=sjolley.yp.pm@gmail.com \
    --cc=openembedded-core@lists.openembedded.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).