From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>,
<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status 7 March 2023 (WW10)
Date: Tue, 7 Mar 2023 08:40:21 -0700 [thread overview]
Message-ID: <0f2201d9510b$215b4520$6411cf60$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4817 bytes --]
Current Dev Position: YP 4.2 M4
Next Deadline: 3rd April 2023 YP 4.2 M4 Build
Next Team Meetings:
* Bug Triage meeting Thursday March 9th 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Weekly Project Engineering Sync Tuesday March 7th at 8 am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
* Twitch - See <https://www.twitch.tv/theyoctojester>
https://www.twitch.tv/theyoctojester
Key Status/Updates:
* YP 4.2 M3 was released
* YP 4.0.8 is in QA
* YP 4.1.3 is ready for QA
* We are now in feature freeze for 4.2. We are continuing to merge
some version upgrades where the stability of the release is unlikely to be
affected.
* Patches continue to merge into master and there are some good bug
fixes in there
* There is a bugfix for bitbake's XMLRPC server mode but the lack of
bug reports raise a concern about how widely it is being used.
* There are a number of ptest related issues (mostly test naming)
which the new regression reports are highlighting. If anyone is interested
in helping clean up and improve the ptests and toolchain tests, please let
us know.
* CVE levels in the LTS releases are at higher levels than they have
been for a while which is a concern.
* We have a growing number of bugs in bugzilla, any help with them is
appreciated.
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: patchtest, layerindex,
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>
https://wiki.yoctoproject.org/wiki/Newcomers
* There are bugs that are currently unassigned for YP 4.2. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhan
cements.2FBugs
* 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/mai
ntainers.inc>
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.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>
https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
* Help us resolve CVE issues:
<https://autobuilder.yocto.io/pub/non-release/patchmetrics/> CVE metrics
YP 4.2 Milestone Dates:
* YP 4.2 M3 is released
* YP 4.2 M4 build date 2023/04/03
* YP 4.2 M4 Release date 2023/04/28
Upcoming dot releases:
* YP 4.0.8 is built and in QA
* YP 4.1.3 is built
* YP 4.1.3 Release date 2023/03/17
* YP 3.1.24 build date 2023/03/20
* YP 3.1.24 Release date 2023/03/31
* YP 4.0.9 build date 2023/04/10
* YP 4.0.9 Release date 2023/04/21
* YP 4.1.4 build date 2023/05/01
* YP 4.1.4 Release date 2023/05/13
* YP 3.1.25 build date 2023/05/08
* YP 3.1.25 Release date 2023/05/19
* YP 4.0.10 build date 2023/05/15
* YP 4.0.10 Release date 2023/05/26
Tracking Metrics:
* WDD 2497 (last week 2442) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
* Total patches found: 1185 (last week 1183)
* Patches in the Pending State: 277 (23%) [last week 277 (23%)]
* <https://autobuilder.yocto.io/pub/non-release/patchmetrics/>
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>
https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at:
<https://wiki.yoctoproject.org/wiki/Weekly_Status>
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: sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com>
[-- Attachment #2: Type: text/html, Size: 42560 bytes --]
reply other threads:[~2023-03-07 15:40 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='0f2201d9510b$215b4520$6411cf60$@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