Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW03'20
Date: Tue, 14 Jan 2020 07:52:31 -0800	[thread overview]
Message-ID: <074801d5caf2$a160cdf0$e42269d0$@gmail.com> (raw)

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

Current Dev Position: YP 3.1 M2

Next Deadline: YP 3.1 M2 build date 1/20/2020

 

Next Team Meetings:

*	Bug Triage meeting Thursday Jan. 16th  at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
*	Monthly Project Meeting Tuesday Feb. 4th  at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Weekly Engineering Sync Tuesday Jan. 14th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Twitch - Next event is Tuesday Jan. 14th at 8am PDT (
<https://www.twitch.tv/yocto_project> https://www.twitch.tv/yocto_project)

 

Tip of the Week:

*	'oe-pkgdata-browser' is a new handy small helper UI added by Ross to
visualise the pkgdata held within a build.
*	(anyone with tips they'd like to see here, please send to Stephen or
Richard)

 

Key Status/Updates:

*	YP 3.1 M2 is due to be built next week.
*	Patch merging is roughly on track however there are a number of
failures identified with key patches (glibc has a prelink issue on mips,
python 3.8 upgrade blocked on uid issue, gstreamer meson transition blocked
on nodistro failure). Most of these issues are making progress over time.
*	The more worrying aspect is that there are a number of
recurring/intermittent failures in the automated testing, mostly from
selftest and testimage.
*	Looking at the build history, "full" images have built cleanly only
once in the past month (3 times in the last two months), which is a pretty
shocking statistic which summarises the challenges we face there. Most of
these are being procrastinated on by the bug owners since we can't reproduce
them at will. We really need help working on these kinds of issues.
*	We have changed the sstate mirrors to be per release, simply to
lower the numbers of files in any given sstate directory.
*	The triage team is worried about attendance at triage meetings and
the project is finding it hard to find people to help fix bugs. If anyone is
willing to work on bugs, assistance would be greatly appreciated.

 

YP 3.1 Milestone Dates:

*	YP 3.1 M2 build date 1/20/2020
*	YP 3.1 M2 release date 1/31/2020
*	YP 3.1 M3 build date 2/24/2020
*	YP 3.1 M3 release date 3/6/2020
*	YP 3.1 M4 build date  3/30/2020
*	YP 3.1 M4 release date  4/24/2020

 

Planned upcoming dot releases:

*	YP 2.7.3 build date  2/10/2020
*	YP 2.7.3 release date 2/21/2020
*	YP 3.0.2 build date  2/3/2020
*	YP 3.0.2 release date 2/14/2020

 

Tracking Metrics:

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

*	Total patches found: 1411 (last week 1400)
*	Patches in the Pending State: 562 (40%) [last week 562 (40%)]

 

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 Project Manager

*    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@gmail.com

 


[-- Attachment #2: Type: text/html, Size: 36198 bytes --]

             reply	other threads:[~2020-01-14 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 15:52 sjolley.yp.pm [this message]
2020-01-14 18:39 ` [yocto] Yocto Project Status WW03'20 akuster808

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='074801d5caf2$a160cdf0$e42269d0$@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