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 WW26'20
Date: Tue, 30 Jun 2020 07:52:46 -0700	[thread overview]
Message-ID: <240c01d64eee$1e6ab160$5b401420$@gmail.com> (raw)

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

Current Dev Position: YP 3.2 M2

Next Deadline: YP 3.2 M2 build date 2020/7/27

 

Next Team Meetings:

*	Bug Triage meeting Thursday July 2nd at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
*	Monthly Project Meeting Tuesday July 7th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Weekly Engineering Sync Tuesday July 14th  at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*	YP 3.2 M1 was released.
*	We've updated to a new version of the buildtools tarball for master
and dunfell
*	We continue to be concerned about autobuilder stability, we're
continuing to see high numbers of intermittent failures. You can see the
list of failures we're seeing 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 is urgently needed to bring these to a manageable level.

*	We are struggling with maintainers for some key components of the
system/infrastructure such as devtool, wic, buildhistory and
patchwork/patchtest. If anyone can help in these areas please contact
Richard.
*	If anyone has thoughts on attracting and recognising project
contributors and contributions, we would be interested in ideas and
assistance in that area.
*	It is ELC this week, please stop by the booth and/or ELC
#2-track-yocto-project slack channel and say hi. There are still places
available on our virtual Developer Day:
<https://events.linuxfoundation.org/yocto-dev-day-north-america/>
https://events.linuxfoundation.org/yocto-dev-day-north-america/
*	Another way to help the project is to help us with bugs that are
currently unassigned but ideally needed during 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're pleased to announce we have a new manual in the Yocto Project
documentation 'bookshelf' which covers the project's testing processes and
infrastructure including the autobuilder and resulttool. A work-in-progress
version of this can be viewed here:
<https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html>
https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html. So
far, it contains basic information in key areas, we're happy to take
feedback on areas that are missing or need more information and/or take
contributions to further extend this work.

 

YP 3.2 Milestone Dates:

*	YP 3.2 M1 is released.
*	YP 3.2 M2 build date 2020/7/27
*	YP 3.2 M2 Release date 2020/8/7
*	YP 3.2 M3 build date 2020/8/31
*	YP 3.2 M3 Release date 2020/9/11
*	YP 3.2 M4 build date 2020/10/5
*	YP 3.2 M4 Release date 2020/10/30

 

Planned upcoming dot releases:

*	YP 3.0.4 build date 2020/8/10
*	YP 3.0.4 release date 2020/8/21
*	YP 3.1.2 build date 2020/9/14
*	YP 3.1.2 release date 2020/9/25

 

Tracking Metrics:

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

*	Total patches found: 1272 (last week 1298)
*	Patches in the Pending State: 498 (39%) [last week 518 (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 Program Manager

*    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com> 

 


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

                 reply	other threads:[~2020-06-30 14:52 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='240c01d64eee$1e6ab160$5b401420$@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