Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <sjolley.yp.pm@gmail.com>
To: <yocto@lists.yoctoproject.org>,
	<openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW05`22
Date: Mon, 31 Jan 2022 19:37:48 -0700	[thread overview]
Message-ID: <0c8701d81714$b410bc10$1c323430$@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 5381 bytes --]

Current Dev Position: YP 3.5 M3

Next Deadline: 21th Feb. 2022 YP 3.5 M3 build

 

Next Team Meetings:

*	Bug Triage meeting Thursday Feb. 3rd 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*	Monthly Project Meeting Tuesday Feb. 1st 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 Feb. 8th 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:

*	YP 3.5 M2 has passed QA with one bug highlighted (14708). Due to
vacations in Asia the release, if approved, will be made next week.
*	YP 3.1.14 is ready for QA but the release will also be delayed until
next week.
*	Upstream glibc are now planning to remove prelink support in 2.36. I
think we will still want to remove prelink from OE-Core before our next
release though, particularly as it is an LTS.
*	An
<https://lists.openembedded.org/g/openembedded-core/message/160881> email
proposing inclusive language changes for bitbake and OE-Core has been sent
to the community for review. The aim is to implement this before M3.
*	We are seeing networking issues during image testing on the
centos8/stream8 workers, possibly due to recent changes in the distro. Help
with debugging this welcome.
*	We have also realized there is an issue with hash equivalence where
the current mechanism will not account for different headers inside the
sysroot added through indirect dependencies (e.g. linux-libc-headers via
glibc). This means something like rtcwake in util-linux which uses rtc.h can
have differing debug symbols due to differing line numbers yet otherwise be
identical. There is a potential fix with downsides in master-next.
*
<https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgK
IiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488
&format=interactive> CVE metrics are still under control for master with
pending patches accounted for (thanks Ross!) but work still remains on the
various stable branches which have high counts.
*	Intermittent issues continue to be at record 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

In particular, we're struggling to understand the intermittent network issue
with external hosts we're seeing very occasionally.

 

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.

 

YP 3.5 Milestone Dates:

*	YP 3.5 M2 is out of QA
*	YP 3.5 M3 build date 2022/02/21
*	YP 3.5 M3 Release date 2022/03/04
*	YP 3.5 M4 build date 2022/04/04
*	YP 3.5 M4 Release date 2022/04/29

 

Upcoming dot releases:

*	YP 3.1.14 is built
*	YP 3.1.14 Release date 2022/02/04
*	YP 3.4.2 build date 2022/02/07
*	YP 3.4.2 Release date 2022/02/18
*	YP 3.3.5 build date 2022/02/14
*	YP 3.3.5 Release date 2022/02/25
*	YP 3.1.15 build date 2022/03/14
*	YP 3.1.15 Release date 2022/03/25
*	YP 3.4.3 build date 2022/03/21
*	YP 3.4.3 Release date 2022/04/01
*	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 2705 (last week 2700) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*	OE-Core/Poky Patch Metrics

*	Total patches found: 1236 (last week 123.)
*	Patches in the Pending State: 342 (28%) [last week 340 (28%)]

 

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: 43142 bytes --]

             reply	other threads:[~2022-02-01  2:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01  2:37 sjolley.yp.pm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-01 16:07 Yocto Project Status WW05`22 sjolley.yp.pm

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='0c8701d81714$b410bc10$1c323430$@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