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 26 March 2024 (WW13)
Date: Tue, 26 Mar 2024 07:46:57 -0700 [thread overview]
Message-ID: <CAK5yBb-Ht_6tQh5VXdr6WHnfnU=bPL9J5Np-61NGp7yBnRwQTw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5376 bytes --]
Current Dev Position: YP 5.0 M4 - Final Release
Next Deadline: 1st April 2024 YP 5.0 M4 build
Next Team Meetings:
-
Bug Triage meeting Thursday March 28th at 7:30 am PST (
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
-
Weekly Project Engineering Sync Tuesday March 26th 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 M3 has been released.
-
YP 4.0.17 is under review and due for release.
-
Steve is taking patches for Dunfell until around April 8 in preparation
for an April 15 build. This will be the last release of dunfell.
-
There was a regression on beaglebone in 5.0 M3 where X11 wasn’t working
but this has been fixed in master ready for the release.
-
A key worry now is the documentation for the release, especially given
it is an LTS. There are emails on the docs list about this, help is much
appreciated.
-
For M4, we are still hoping to transition to a different public hash
equivalence server before release. We have stopped taking general point
release upgrades to recipes unless there is a security or other key reason
to take them. The key remaining fix needed before building is for the opkg
lock issue.
-
The opkg lock issue is now understood but the best fix is still under
discussion/ development.
-
One set of the problematic autobuilder failures was tracked down to a
queued but unmerged bitbake patch. There are other intermittent issues
which still need to be root caused, at least one failure was also due to
system load issues.
-
We continue to watch the NIST NVD (CVE database) issue and await further
information about what the future holds there (https://nvd.nist.gov/ -
“You will temporarily see delays in analysis efforts during this
transition”)
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 is released.
-
YP 5.0 M4 build date 2024/04/01
-
YP 5.0 M4 Release date 2024/04/30
Upcoming dot releases:
-
YP 4.0.17 is out of QA.
-
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 2703 (last week 2706) (
https://wiki.yoctoproject.org/charts/combo.html)
-
OE-Core/Poky Patch Metrics
-
Total patches found: 1156 (last week 1148)
-
Patches in the Pending State: 249 (22%) [last week 249 (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: 36640 bytes --]
reply other threads:[~2024-03-26 14:47 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='CAK5yBb-Ht_6tQh5VXdr6WHnfnU=bPL9J5Np-61NGp7yBnRwQTw@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).