From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>,
<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW35`21
Date: Tue, 31 Aug 2021 07:49:17 -0700 [thread overview]
Message-ID: <139401d79e77$60681650$213842f0$@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4232 bytes --]
Current Dev Position: YP 3.4 M3 (Feature Freeze)
Next Deadline: 23rd Aug. 2021 YP 3.4 M3 build (Feature Freeze)
Next Team Meetings:
* Bug Triage meeting Thursday Sept. 2nd at 7:30am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
* Monthly Project Meeting Tuesday Sept. 7th 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 Aug. 31th 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:
* We are now at feature freeze for YP 3.4
* Rust was merged into core, it was touch and go whether we
could/would or not. Unfortunately there was an error found after merging
with cargo-native on centos7 hosts which we still need to resolve before
building M3.
* Fixes for glibc 2.34 and pseudo were merged however this uses a
binary shim and isn't an ideal way to solve the issues. We need to find a
way to have active development on pseudo with investigation into possible
replacement approaches.
* A kernel issue introduced in recent kernel module versioning changes
needs to resolved before we can build M3.
* The glibc 2.34 upgrade caused issues with docker and the clone3
syscall returning EPERM instead of ENOSYS. We will likely have to add a
workaround to our glibc until released versions of docker have the upstream
fix.
* Intermittent issues are ongoing and 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
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 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.1.11 build date 2021/09/13
* YP 3.1.11 release date 2021/9/24
Tracking Metrics:
* WDD 2633 (last week 2610) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
* Total patches found: 1301 (last week 1299)
* Patches in the Pending State: 482 (37%) [last week 484 (37%)]
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: 39030 bytes --]
reply other threads:[~2021-08-31 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='139401d79e77$60681650$213842f0$@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