From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW28`21
Date: Tue, 13 Jul 2021 07:56:03 -0700 [thread overview]
Message-ID: <136501d777f7$34416f50$9cc44df0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4612 bytes --]
Current Dev Position: YP 3.4 M2
Next Deadline: 12th July 2021 YP 3.4 M2 build
Next Team Meetings:
* Bug Triage meeting Thursday July 15th at 7:30am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Monthly Project Meeting Tuesday July 13th at 8am PDT (
<https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09>
https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
<https://zoom.us/j/990892712> )
* Weekly Engineering Sync Tuesday July 20th at 8am 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:
* An issue with eSDK being host specific due to pseudo-native host
dependencies has been resolved and this should resolve a number of bugs
being reported by the community around use of the eSDK.
* The prserv rewrite is still pending on resolving the issues with
python asyncio.
* We are continuing to make progress on the intermittent autobuilder
failures. A race was identified in the qemu networking lock handling and
there were some reproducibility fixes. Tweaks have been made to the
autobuilder configuration such as avoiding key generation in more cases
which it is believed may have been running into entropy shortages on the
hosts, or just hitting CPU load issues. Some ptest improvements have also
been made.
* Despite this progress, we continue to see intermittent issues,
particularly ptest ones. Help is very much welcome on these 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
* The multiconfig changes in bitbake continue to cause problems, we
still need simpler test cases to reproduce issues rather than huge builds.
The existing patches seem to fix some workloads and break others and current
test cases are very slow to work with.
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.4. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.4_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.4_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.
YP 3.4 Milestone Dates:
* YP 3.4 M2 build date 2021/07/12
* YP 3.4 M2 Release date 2021/07/23
* YP 3.4 M3 build date 2021/08/23 (Feature Freeze)
* YP 3.4 M3 Release date 2021/09/03
* YP 3.4 M4 build date 2021/10/04
* YP 3.4 M4 Release date 2021/10/29
Planned upcoming dot releases:
* YP 3.3.2 build date 2021/07/19
* YP 3.3.2 release date 2021/07/30
* YP 3.1.10 build date 2021/07/26
* YP 3.1.10 release date 2021/08/06
* YP 3.1.11 build date 2021/09/13
* YP 3.1.11 release date 2021/9/24
Tracking Metrics:
* WDD 2658 (last week 2668) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
* Total patches found: 1284 (last week 1276)
* Patches in the Pending State: 480 (37%) [last week 481 (38%)]
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: 40253 bytes --]
reply other threads:[~2021-07-13 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='136501d777f7$34416f50$9cc44df0$@gmail.com' \
--to=sjolley.yp.pm@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@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