public inbox for openembedded-core@lists.openembedded.org
 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 6 September 2022 (WW36)
Date: Tue, 6 Sep 2022 07:41:59 -0700	[thread overview]
Message-ID: <00ed01d8c1fe$d2958d60$77c0a820$@gmail.com> (raw)

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

Current Dev Position: YP 4.1 M3 (Feature Freeze)

Next Deadline: 22nd August 2022 YP 4.1 M3 Build

 

Next Team Meetings:

*	Bug Triage meeting Thursday September 8th 7:30 am PDT (
<https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09>
https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*	Weekly Project Engineering Sync Tuesday September 6th 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:

*	We are now at feature freeze for 4.1 but M3 has not been built yet.
*	Many of the blocking issues for M3 have been resolved including:

*	perl build hangs
*	cve-check database issues
*	hash-equiv file not found issues on local domain sockets
*	layer setup changes merged
*	rust upgrade merged
*	libgcrypt ptest issues on ARM is potentially fixed
*	llvm build path corruption in mesa was resolved
*	rust ppc patch was revised
*	llvm-config handling in core was reworked
*	nativesdk-gcc issue breaking rust SDK tests was identified and fixed
*	a checksum mismatch race issue in bitbake's fetcher code was fixed

*	Thanks to everyone who helped work on and resolve these, it will
significantly improve the release and autobuilder stability during testing.
*	There is still an issue with rust SDK failures on ubuntu1804 to
resolve before M3 can build
*	The rust selftest changes are looking unlikely to merge as they
don't pass during testing yet and one of the precursor patches causes
buildpath issues. Some precursor patches did merge.
*	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

 

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 4.1. See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_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 4.1 Milestone Dates:

*	YP 4.1 M3 build date 2022/08/22
*	YP 4.1 M3 Release date 2022/09/02
*	YP 4.1 M4 build date 2022/10/03
*	YP 4.1 M4 Release date 2022/10/28

 

Upcoming dot releases:

*	YP 4.0.4 build date 2022/09/19
*	YP 4.0.4 Release date 2022/09/30
*	YP 3.1.20 build date 2022/10/10
*	YP 3.1.20 Release date 2022/10/21
*	YP 4.0.5 build date 2022/10/31
*	YP 4.0.5 Release date 2022/11/11

 

Tracking Metrics:

*	WDD 2459 (last week 2469) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*	OE-Core/Poky Patch Metrics

*	Total patches found: 1221 (last week 1224)
*	Patches in the Pending State: 314 (26%) [last week 329 (27%)]

*	 <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: 56188 bytes --]

                 reply	other threads:[~2022-09-06 14:42 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='00ed01d8c1fe$d2958d60$77c0a820$@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