Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Yocto Discussion <yocto@yoctoproject.org>,
	OpenEmbedded List <openembedded-core@lists.openembedded.org>
Subject: Yocto Project Status WW28
Date: Fri, 08 Jul 2016 09:11:09 -0700	[thread overview]
Message-ID: <1467994269.6912.374.camel@linux.intel.com> (raw)

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

Current Dev Position: YP 2.2 M2
Next Deadline: YP 2.2 M2 cut off would
be: 7/18/16

SWAT team rotation: Bill -> Paul
https://wiki.yoctoproject.org/wiki/Yoct
o_Build_Failure_Swat_Team

Key Status/Updates:
 * M1 QA report is out however there are concerns about performanceregressions which have not been root caused. M1 will continue to bedelayed until we figure out those issues and the fact that medium+ bugsand high bugs are still assigned to M1.
 * M2 patch merging is held up due to the shear volume of regressionswe’re seeing which are basically being left to Ross/RP to triage andfind the patches responsible. 
 * We did upgrade pseudo after various issues which brings in severalxattr fixes and resolves the init problems we were seeing in pseudotowards the end of the last release properly, rather than theworkarounds we put in place.
 * We’ve merged the progress patches from Paul so we get better feedbackduring the build for how various tasks are progressing.
 * We’re looking likely to remove directfb from OE-Core since the projectappears to have died.
 * 2.1.1 is in QA having had a successful build. We are working with areduced capacity QA team due to various changes at Intel/WindRiver sowe will have more limited QA testing of this unfortunately.

Key YP 2.2 Dates:
 * YP 2.2 M1 release would be: 6/24/16
 * YP 2.2 M2 cut off would be: 7/18/16
 * YP 2.2 M2 release would be: 7/29/16
 * YP 2.2 M3 cut off would be: 8/29/16
 * YP 2.2 M3 release would be: 9/9/16
 * YP 2.2 M4 cut off would be: 10/3/16
 * YP 2.2 M4 release would be: 10/28/16

Tracking Metrics:
	WDD 2747 (last week 2718)
(https://wiki.yoctoproject.org/charts/combo.html)

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

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

             reply	other threads:[~2016-07-08 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 16:11 Saul Wold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-10 15:15 Yocto Project Status WW28 Jolley, Stephen K

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=1467994269.6912.374.camel@linux.intel.com \
    --to=sgw@linux.intel.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