Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Stephen Jolley" <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW39'20
Date: Tue, 29 Sep 2020 08:00:20 -0700	[thread overview]
Message-ID: <0e6401d69671$40a1ba60$c1e52f20$@gmail.com> (raw)

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

Current Dev Position: YP 3.2 M4

Next Deadline: YP 3.2 M4 Feature Freeze - Now

 

Next Team Meetings:

*	Bug Triage meeting Thursday Oct. 1st at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
*	Monthly Project Meeting Tuesday Oct. 6th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Weekly Engineering Sync Tuesday Sept. 29th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*	YP M3 rc2 has been through QA. We have resolved the beaglebone and
bitbake UI issues, the ptest issues remain and need attention in M4. It is
likely M3 rc2 will be released.
*	YP 3.1.3 is currently going through QA.
*	Unfortunately intermittent autobuilder issues, whilst reduced, do
still remain.
*	Issues with file mode corruption in pseudo have been identified and
we're concerned this may be going undetected in the majority of cases. The
issue uncovered would explain several odd bugs we've seen over the last few
years where file mode bits have disappeared. There are some experimental
pseudo patches available that reduce the impact and frequency of these
issues but as yet we don't have a full solution. We're hampered by a lack of
a pseudo maintainer with both the availability and experience to be able to
help.
*	We continue to struggle with a number of autobuilder intermittent
bugs. 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

Help with any of these would be much appreciated, unfortunately it is
proving hard to find anyone interested in helping figure these out and they
significantly hamper our testing.

 

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

*	YP 3.2 M3 is out of QA and should release soon.
*	YP 3.2 M4 build date 2020/10/5
*	YP 3.2 M4 Release date 2020/10/30

 

Planned upcoming dot releases:

*	YP 3.1.3 is built and in QA
*	YP 3.1.4 build date 2020/11/2
*	YP 3.1.4 release date 2020/11/13

 

Tracking Metrics:

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

*	Total patches found: 1270 (last week 1268)
*	Patches in the Pending State: 493 (39%) [last week 496 (39%)]

 

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

                 reply	other threads:[~2020-09-29 15:00 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='0e6401d69671$40a1ba60$c1e52f20$@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