From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mail.openembedded.org (Postfix) with ESMTP id 487966E5CB for ; Fri, 29 Jul 2016 15:37:28 +0000 (UTC) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP; 29 Jul 2016 08:37:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,440,1464678000"; d="scan'208,217";a="741536804" Received: from swold-mobl2.amr.corp.intel.com ([10.254.5.132]) by FMSMGA003.fm.intel.com with ESMTP; 29 Jul 2016 08:37:29 -0700 Message-ID: <1469806649.3175.93.camel@linux.intel.com> From: Saul Wold To: Yocto Discussion , OpenEmbedded List Date: Fri, 29 Jul 2016 08:37:29 -0700 X-Mailer: Evolution 3.20.4 (3.20.4-1.fc24) Mime-Version: 1.0 Subject: Yocto Project Status WW31 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, 29 Jul 2016 15:37:29 -0000 Content-Type: multipart/alternative; boundary="=-xB9mZfP3y07VOGgoOGY5" --=-xB9mZfP3y07VOGgoOGY5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Current Dev Position: YP 2.2 M3 Next Deadline: YP 2.2 M3 which will be Aug 29th (5:00pm GMT) SWAT team rotation: Ross -> Randy https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * This status covers two weeks * We did get an M2 build into QA, it took some time to stabilize due to the shear number of errors we ran into coming from submitted patches, particularly from oe-selftest which takes a long time to run. * A performance regressing in the printk kernel feature was identified, proving the value in monitoring these things, wish we had more eyes on it though. * The M2 QA report is out. Unfortunately there are a substantial number of bugs being reported against M2. There is no common theme, bugs in many aspects of the system. We’re undecided whether to release it as is, try an rc2 with bugs fixed on a branch or try an rc2 with current master which does address some of the issues. * https://wiki.yoctoproject.org/wiki/WW30_-_2016-07-21_-_Full_Test_Cycle_2.2_M2.rc1 * We’ve decided to remove uclibc. * Performance issues with pseudo when using xattrs have been identified and are in testing. * 2.1.1 has gcc6 fixes merged. We have some checkuri fixes pending, then will run a 2.1.1 rc2 build. 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 2744 (last week 2698) (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!] --=-xB9mZfP3y07VOGgoOGY5 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable


Current Dev Position:= YP 2.2 M3

Next Deadline: YP 2.2 M3 which wi= ll be Aug 29th (5:00pm GMT)


SWAT team ro= tation: Ross -> Randy

https://wiki.yoctoproject= .org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  • This status covers two weeks

  • We d= id get an M2 build into QA, it took some time to stabilize due to the shear= number of errors we ran into coming from submitted patches, particularly f= rom oe-selftest which takes a long time to run.

  • A = performance regressing in the printk kernel feature was identified, proving= the value in monitoring these things, wish we had more eyes on it though.<= /span>

  • The M2 QA report is out. Unfortunately there are a= substantial number of bugs being reported against M2. There is no common t= heme, bugs in many aspects of the system. We=E2=80=99re undecided whether t= o release it as is, try an rc2 with bugs fixed on a branch or try an rc2 wi= th current master which does address some of the issues.

    • https://wiki.yoctoproject.org/wiki/WW30_-_2016-07= -21_-_Full_Test_Cycle_2.2_M2.rc1

  • We=E2=80=99= ve decided to remove uclibc.

  • <= p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;">= Performance issues wi= th pseudo when using xattrs have been identified and are in testing.=

  • 2.1.1 has gcc6 fixes merged. We have some checkuri fixes= pending, then will run a 2.1.1 rc2 build.


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 of= f 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 2744 (last week 2698)

(https://wiki.yoctoproject.org/charts/combo.html<= /a>)


Key Status L= inks for YP:

https://wiki.yoctoproject.org/wiki/Yocto_= Project_v2.2_Status

https://wiki.yoctoproject.org/wiki/Yo= cto_2.2_Schedule

https://wiki.yoctoproject.org/wiki/Yocto= _2.2_Features


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


--=-xB9mZfP3y07VOGgoOGY5--