All of lore.kernel.org
 help / color / mirror / Atom feed
From: <sjolley.yp.pm@gmail.com>
To: <yocto@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW26'19
Date: Tue, 25 Jun 2019 10:22:41 -0700	[thread overview]
Message-ID: <039e01d52b7a$990d2e40$cb278ac0$@gmail.com> (raw)

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

Current Dev Position: YP 2.8 M2

Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019

 

SWAT Team Rotation:

*	SWAT lead is currently: Ross
*	SWAT team rotation: Ross -> Amanda on June 28, 2019
*	SWAT team rotation: Amanda -> Chen on July, 5, 2019
*	 <https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team>
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*	Bug Triage meeting Thursday June 27th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
*	Monthly Project Meeting Tuesday July 2nd at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712) 
*	Twitch - Next event is Tuesday 9th July at 8am PDT (
<https://www.twitch.tv/yocto_project> https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*	2.8 M1 has been released.
*	Mailing lists issues are continuing to be worked on as a top
priority.
*	We have a new "newcomer" bug category which are bugs suited to
someone new to the project. These can be seen here:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*	Several key reproducibility fixes have merged, thanks Joshua!
*	The autobuilder has suffered stability issues with its NFS setup,
seemingly related to the increased load from the new servers. We're
monitoring changes, hoping they fix the issue.
*	We had significant problems with the versioning of libcrypt in
recent distros which resulted in the need for a new uninative release. This
fixes autobuilder builds.

 

Planned Releases for YP 2.8:

*	M2 Cutoff 14th July
*	M2 Release 26th July
*	M3 Cutoff (Feature Freeze) 25th Aug
*	M3 Release 6th Sept
*	M4 Cutoff 30th Sept
*	2.8 (M4) Final Release 25th Oct

 

Planned upcoming dot releases:

*	YP 2.7.1 (Warrior) is planned for build imminently now that 2.8 M1
is done but is pending the new uninative changes.
*	YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and
before 2.8 M2

 

Tracking Metrics:

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

*	Total patches found: 1509 (last week 1511)
*	Patches in the Pending State: 638 (42%) [last week 641 (43%)]

 

Key Status Links for YP:

 <https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 <https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule>
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 <https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features>
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

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
<mailto:sjolley.yp.pm@gmail.com> 

 


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

             reply	other threads:[~2019-06-25 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 17:22 sjolley.yp.pm [this message]
2019-06-25 18:44 ` [yocto] Yocto Project Status WW26'19 akuster808
2019-06-25 18:44   ` 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='039e01d52b7a$990d2e40$cb278ac0$@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.