From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>,
<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status 25 July 2023 (WW30)
Date: Tue, 25 Jul 2023 07:48:58 -0700 [thread overview]
Message-ID: <004e01d9bf07$25148b80$6f3da280$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5395 bytes --]
Current Dev Position: YP 4.3 M3
Next Deadline: 28th August 2023 YP 4.3 M3 build date
Next Team Meetings:
* Bug Triage meeting Thursday July 27th 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Weekly Project Engineering Sync Tuesday July 25th 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.2 was released
* YP 4.3 M2 has been through QA with one issue found (bug 15170) and
is being reviewed by the TSC
* YP 3.1.27 is in QA
* Toolchain tests have continued to improve with rust tests added and
3,344,888
tests now being run with failures reduced to 8,373 (down from 210,000).
* Issues in the LTP test parsing were identified and fixing this
should improve the reliability of test reports.
* The regression report for M2 is definitely improved on previous
versions with the important data becoming clearer:
<https://autobuilder.yocto.io/pub/releases/yocto-4.3_M2.rc1/testresults/test
result-regressions-report.txt>
https://autobuilder.yocto.io/pub/releases/yocto-4.3_M2.rc1/testresults/testr
esult-regressions-report.txt
* We're considering switching to a pre-release version of autoconf due
to improvements in largefile/64 bit time support.
* The project RFQ deadline has now passed, thanks to everyone who
submitted. The project aims to process the responses and respond in the next
couple of weeks.
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.3. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_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
* We have a growing number of bugs in bugzilla, any help with them is
appreciated.
YP 4.3 Milestone Dates:
* YP 4.3 M2 is back from QA
* YP 4.3 M3 build date 2023/08/28
* YP 4.3 M3 Release date 2023/09/08
* YP 4.3 M4 build date 2023/10/02
* YP 4.3 M4 Release date 2023/10/27
Upcoming dot releases:
* YP 4.2.2 is released
* YP 3.1.27 is in QA
* YP 4.0.12 build date 2023/08/07
* YP 4.0.12 Release date 2023/08/18
* YP 4.2.3 build date 2023/08/28
* YP 4.2.3 Release date 2023/09/08
* YP 3.1.28 build date 2023/09/18
* YP 3.1.28 Release date 2023/09/29
* YP 4.0.13 build date 2023/09/25
* YP 4.0.13 Release date 2023/10/06
* YP 3.1.29 build date 2023/10/30
* YP 3.1.29 Release date 2023/11/10
* YP 4.0.14 build date 2023/11/06
* YP 4.0.14 Release date 2023/11/17
* YP 4.2.4 build date 2023/11/13
* YP 4.2.4 Release date 2023/11/24
* YP 3.1.30 build date 2023/12/11
* YP 3.1.30 Release date 2023/12/22
* YP 4.0.15 build date 2023/12/18
* YP 4.0.15 Release date 2023/12/29
Tracking Metrics:
* WDD 2487 (last week 2477) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
* Total patches found: 1145 (last week 1146)
* Patches in the Pending State: 260 (23%) [last week 260 (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: 51615 bytes --]
reply other threads:[~2023-07-25 14:49 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='004e01d9bf07$25148b80$6f3da280$@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.