From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>,
<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW132`22
Date: Tue, 29 Mar 2022 07:56:33 -0700 [thread overview]
Message-ID: <0e3601d8437d$2f088490$8d198db0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4972 bytes --]
Current Dev Position: YP 3.5 M4
Next Deadline: 4th April. 2022 YP 3.5 M4 build
Next Team Meetings:
* Bug Triage meeting Thursday Mar. 31st 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Monthly Project Meeting Tuesday Apr. 5th at 8 am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
* Weekly Engineering Sync Tuesday Mar. 29th 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
Key Status/Updates:
* The first release candidate build for YP 4.0 (3.5) is due next week
(Monday, 4th April)
* YP 3.1.15 was released
* YP 3.4.3 has passed QA and likely to be released imminently
* We're calming down the number of changes going into the release at
this point including upgrades. For example the recent go uprev is very
unlikely to make it in at this point. If there are patches you think should
be in the release, please comment on them to show support.
* We were able to isolate one parsing process lockup which ideally
we'd fix in the release but it is unclear if the fixes will be ready.
* YP 4.1 planning document is available for review at:
<https://docs.google.com/document/d/1-g7DatSdmIETwD3xFSCxV7MbWVVkpQvQ788mIr1
MPTI/edit?usp=sharing>
https://docs.google.com/document/d/1-g7DatSdmIETwD3xFSCxV7MbWVVkpQvQ788mIr1M
PTI/edit?usp=sharing
* Improvements to the documentation version number handling were made,
making things easier for release engineering and general maintenance. It
should also improve the items in the switcher dropdown menu, Please report
any issues anyone spots with the docs.
* If people see intermittent issues in their own builds, particularly
if they're the same as intermittent issues seen on the autobuilder, please
do comment in the bugs mentioning when they happen as the frequency
information does help us prioritize fixing the most common issues.
* Intermittent issues continue to be at high levels and help is very
much welcome in trying to resolve them. 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
We did work out the cause of the infamous tinfoil wait_event intermittent
issue.
Ways to contribute:
* 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 3.5. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_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 us resolve CVE issues:
<https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgK
IiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488
&format=interactive> CVE metrics
YP 3.5 Milestone Dates:
* YP 3.5 M4 build date 2022/04/04
* YP 3.5 M4 Release date 2022/04/29
Upcoming dot releases:
* YP 3.1.15 is released.
* YP 3.4.3 is near release.
* YP 3.3.6 build date 2022/03/28
* YP 3.3.6 Release date 2022/04/08
* YP 3.1.16 build date 2022/04/25
* YP 3.1.16 Release date 2022/05/06
Tracking Metrics:
* WDD 2609 (last week 2680) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
* Total patches found: 1191 (last week 1189)
* Patches in the Pending State: 340 (29%) [last week 340 (29%)]
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: 41233 bytes --]
reply other threads:[~2022-03-29 14:56 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='0e3601d8437d$2f088490$8d198db0$@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