($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Neal Caidin <ncaidin@linuxfoundation.org>
To: yocto@lists.yoctoproject.org,
	 OE-core <openembedded-core@lists.openembedded.org>,
	 yocto-status@lists.yoctoproject.org
Subject: Yocto Project Status 30 April 2024 (WW18)
Date: Tue, 30 Apr 2024 10:51:42 -0400	[thread overview]
Message-ID: <CAODMxsLV4sgKkoRErQYda9OPsLH2o4r2Kn+M4C98Ce8iMxiVSg@mail.gmail.com> (raw)

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

Current Dev Position: YP 5.1 M1

Next Deadline: YP 5.1 M1 Build 20 May 2024

Next Team Meetings:

   -

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

   Weekly Project Engineering Sync Tuesday April 30th 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:

   -

   YP 5.0 has been released!
   -

   Huge thanks to everyone who contributed to 5.0
   -

   YP 3.1.33 has passed QA and is due to release
   -

   YP 4.0.18 is in QA.
   -

   Updates to graphing on the patch/CVE metrics page merged
   -

   There is an open letter the project has created related to the CVE/NVD
   situation, more information is available here:
   https://lists.openembedded.org/g/openembedded-architecture/message/1990

Please consider signing this to show support for those changes, which would
improve our ability to analyze CVEs, and that of many other projects
(including other distros) to do so too.

   -

   We continue to watch the NIST NVD (CVE database) situation, the lack of
   CPE information is problematic for us and we are considering what
   alternatives we have. The CVE Project announced support for more
   information fields on CVEs which is a good start.
   -

   Some CVE information is being provided for issues in meta-openembedded,
   this has been provided with help from the Sovereign Tech Fund.
   -

   The project is sponsoring Syslinbit to separate out our CVE tooling from
   the build system into a standalone tool so that it can be used on software
   manifests of output at a later date.
   -

   There are proposals on the openembedded-architecture list to rework how
   do_unpack works, switching it from WORKDIR to a new variable and changing
   some directory layout.


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.1. See:
   https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_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.1 Milestone Dates:

   -

   YP 5.1 M1 Build date  2024-05-20
   -

   YP 5.1 M1 Release date 2024-05-31
   -

   YP 5.1 M2 Build date  2024-07-08
   -

   YP 5.1 M2 Release date 2024-07-19
   -

   YP 5.1 M3 Build date  2024-08-26
   -

   YP 5.1 M3 Release date 2024-09-06
   -

   YP 5.1 M4 Build date  2024-09-30
   -

   YP 5.1 M4 Release date 2024-10-25


Upcoming dot releases:

   -

   YP 3.1.33 is in QA
   -

   YP 4.0.18 is in QA


   -

   YP 5.0.1 Build Date 2024-05-13
   -

   YP 5.0.1 Release Date 2024-05-24
   -

   YP 4.0.19 build date 2024-06-03
   -

   YP 4.0.19 Release date 2024-06-14
   -

   YP 5.0.2 Build Date 2024-06-24
   -

   YP 5.0.2 Release Date 2024-07-05
   -

   YP 4.0.20 Build Date 2024-07-15
   -

   YP 4.0.20 Release Date 2024-07-26
   -

   YP 5.0.3 Build Date 2024-08-12
   -

   YP 5.0.3 Release Date 2024-08-23
   -

   YP 4.0.21 Build Date 2024-09-09
   -

   YP 4.0.21 Release Date 2024-09-20
   -

   YP 5.0.4 Build Date 2024-09-23
   -

   YP 5.0.4 Release Date 2024-10-04
   -

   YP 4.0.22 Build Date 2024-10-14
   -

   YP 4.0.22 Release Date 2024-10-25
   -

   YP 5.0.5 Build Date 2024-11-11
   -

   YP 5.0.5 Release Date 2024-11-22
   -

   YP 4.0.23 Build Date 2024-11-18
   -

   YP 4.0.23 Release Date 2024-11-29


Tracking Metrics:

   -

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

   OE-Core/Poky Patch Metrics
   -

      Total patches found: 1125 (last week 1140)
      -

      Patches in the Pending State: 221 (20%) [last week 245 (21%)]
      -

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


*Neal Caidin*
Program Manager
The Linux Foundation
Durham, NC, U.S.A. - Eastern time zone
+1 (919) 238-9104 (w/h)
+1 (919) 949-1861 (m)
ncaidin@linuxfoundation.org
https://meetings.hubspot.com/ncaidin

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

                 reply	other threads:[~2024-04-30 14:52 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=CAODMxsLV4sgKkoRErQYda9OPsLH2o4r2Kn+M4C98Ce8iMxiVSg@mail.gmail.com \
    --to=ncaidin@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).