From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mail.openembedded.org (Postfix) with ESMTP id CB27360119 for ; Fri, 8 Jul 2016 16:11:09 +0000 (UTC) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP; 08 Jul 2016 09:11:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,330,1464678000"; d="scan'208,217";a="731485113" Received: from swold-mobl2.jf.intel.com ([10.254.96.90]) by FMSMGA003.fm.intel.com with ESMTP; 08 Jul 2016 09:11:09 -0700 Message-ID: <1467994269.6912.374.camel@linux.intel.com> From: Saul Wold To: Yocto Discussion , OpenEmbedded List Date: Fri, 08 Jul 2016 09:11:09 -0700 X-Mailer: Evolution 3.18.5.2 (3.18.5.2-1.fc23) Mime-Version: 1.0 Subject: Yocto Project Status WW28 X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 16:11:10 -0000 Content-Type: multipart/alternative; boundary="=-WIKpIhVZP7+GnimLGfU3" --=-WIKpIhVZP7+GnimLGfU3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit 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!] --=-WIKpIhVZP7+GnimLGfU3 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Current Dev Position: YP 2.2 M= 2

Next Deadline: YP 2.2 M2 cut off would be:= 7/18/16


SWAT team rotation: Bill -> = Paul

https://wiki.yoctoproject.org/wiki/Yocto_Buil= d_Failure_Swat_Team


Key Status/Updat= es:

  • M1 = QA report is out however there are concerns about performance regressions w= hich have not been root caused. M1 will continue to be delayed until we fig= ure out those issues and the fact that medium+ bugs and high bugs are still= assigned to M1.

  • M2 patch merging is held up due = to the shear volume of regressions we=E2=80=99re seeing which are basically= being left to Ross/RP to triage and find the patches responsible. <= /p>

  • We did upgrade pseudo after various issues which brings i= n several xattr fixes and resolves the init problems we were seeing in pseu= do towards the end of the last release properly, rather than the workaround= s we put in place.

  • We=E2=80=99ve merged the progre= ss patches from Paul so we get better feedback during the build for how var= ious tasks are progressing.

  • <= span style=3D"font-size: 14.666666666666666px; background-color: transparen= t; vertical-align: baseline; white-space: pre-wrap;">We=E2=80=99re looking = likely to remove directfb from OE-Core since the project appears to have di= ed.

  • 2.1.1 is in QA having had a successful build. = We are working with a reduced capacity QA team due to various changes at In= tel/WindRiver so we 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/1= 8/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 c= ut off would be: 10/3/16

  • YP 2.2 M4 release would b= e: 10/28/16


Tracking Metrics:<= /span>

WDD 2747 (last week 2718)<= /span>

(https://wiki.yoctopro= ject.org/charts/combo.html)

Key Status Links for YP:

https:/= /wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status

ht= tps://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule

http= s://wiki.yoctoproject.org/wiki/Yocto_2.2_Features


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


--=-WIKpIhVZP7+GnimLGfU3--