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>,
yocto-status@lists.yoctoproject.org
Subject: Yocto Project Status 2 April 2024 (WW14)
Date: Tue, 2 Apr 2024 07:52:47 -0700 [thread overview]
Message-ID: <CAK5yBb9oiGwEF2VprrrtEjHFL3Ja9qQU30wbyBEgL4BzY54CKQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 6969 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 April 4th at 7:30 am PST (
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
-
Weekly Project Engineering Sync Tuesday April 2nd 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 4.0.17 has been released.
-
YP 4.3.4 is in QA and is the final planned nanbield release.
-
YP 5.0 rc1 is now due to build when ready.
-
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.
-
5.0 build status:
-
The opkg lock issue has been worked around for now in the
run-postinsts script
-
An intermittent oe-selftest failure (sstatetests hang) was tracked
down to a race in tinfoil event handling.
-
The public hash equivalence server changes aren’t ready yet
unfortunately
-
There are issues with the size of the buildhistory repository which
is being split up, this needs to happen before we can build 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. This will now be the main delay on the release
timeframe.
-
A new yocto-status <https://lists.yoctoproject.org/g/yocto-status/topics>
mailing list has been created where we plan to send just the project weekly
status reports and any other suitable updates on the project. This should
help those who found the traffic of the other mailing lists too much.
-
A yocto-patches <https://lists.yoctoproject.org/g/yocto-patches/topics>
mailing list has been setup and patches that used to go to the yocto@
list will be migrating over to this new list, making yocto@ a bit more
friendly for questions and discussions.
-
Some other obsolete mailing lists were removed or made read-only to try
and make it easier for people to find the right place to see/send things.
-
Debian 12 and Fedora 40 containers have been added to crops (Thanks Rob
Wolley)
-
All the crops yocto-base containers now include python3-virtualenv
-
The “Binary Distro” work is now well underway and there are PR Server
passthrough patches ready for review. The wiki page
<https://wiki.yoctoproject.org/wiki/Binary_Distro_Prototype#Policies_and_Processes>
has had a number of policy/process proposals documented, at least as a
first pass. Help is welcome to help improve these, or highlight where
further documentation is needed.
-
One year after the original linux.com article, an update was published:
https://www.yoctoproject.org/blog/2024/03/28/maintainer-confidential-challenges-and-opportunities-one-year-on/
-
There was a significant security issue with xz release tarballs. We
never merged the affected version and it was never in any of our main
branches but we did test it on the autobuilder and saw build failures. We
continue to watch for information on any potential implications of that. We
have removed the compromised tarballs from our mirrors.
-
We continue to watch the NIST NVD (CVE database) situation, the recent
update didn’t clarify much. Unfortunately there doesn’t appear to be a
clear path forward as yet.
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 M4 build date 2024/04/01
-
YP 5.0 M4 Release date 2024/04/30
Upcoming dot releases:
-
YP 4.0.17 is released.
-
YP 4.3.4 is in QA.
-
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 2681 (last week 2703) (
https://wiki.yoctoproject.org/charts/combo.html)
-
OE-Core/Poky Patch Metrics
-
Total patches found: 1173 (last week 1156)
-
Patches in the Pending State: 249 (21%) [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: 43672 bytes --]
reply other threads:[~2024-04-02 14:53 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=CAK5yBb9oiGwEF2VprrrtEjHFL3Ja9qQU30wbyBEgL4BzY54CKQ@mail.gmail.com \
--to=sjolley.yp.pm@gmail.com \
--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).