From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by mail.openembedded.org (Postfix) with ESMTP id C585D77117 for ; Fri, 5 Aug 2016 16:30:50 +0000 (UTC) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga104.fm.intel.com with ESMTP; 05 Aug 2016 09:30:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,474,1464678000"; d="scan'208,217";a="744708569" Received: from swold-mobl2.amr.corp.intel.com ([10.255.76.148]) by FMSMGA003.fm.intel.com with ESMTP; 05 Aug 2016 09:30:52 -0700 Message-ID: <1470414650.3175.420.camel@linux.intel.com> From: Saul Wold To: Yocto Discussion , OpenEmbedded List Date: Fri, 05 Aug 2016 09:30:50 -0700 X-Mailer: Evolution 3.20.4 (3.20.4-1.fc24) Mime-Version: 1.0 Subject: Yocto Project Status WW32 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, 05 Aug 2016 16:30:51 -0000 Content-Type: multipart/alternative; boundary="=-qe0GKr7eaYlxSL0K2z1l" --=-qe0GKr7eaYlxSL0K2z1l 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: Randy -> Leo https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * We decided to release M2 with known issues. We have a good handle on some of them, there are others which are unknown but there is no one specific cause of the bugs. * We will run another full QA pass before M3 to try and make sure we are dealing with the known bugs. * Merging of patches continues to be slow as it is proving hard to work out which patches are causing which breakage. The test matrix continues to increase with people being upset if their personal favourite set of options breaks yet we can’t expect to test and catch every regression. We’re not sure what to do about this, the scope of the testing is greater than it ever has been but it does seem to be slowing things down. * A patch for performance issues with pseudo when using xattrs have was merged * 2.1.1 is currently in QA and is expected to be completed early next week, this update contains numerous fixes for for a variety of areas including CVEs, GCC 6.x on Host OS and updated SRC_URIs 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 2714 (last week 2744) (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!] --=-qe0GKr7eaYlxSL0K2z1l Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable


Curren= t Dev Position: YP 2.2 M3

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


SWAT team rotation: Randy -> Leo

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


Key Status/Updates:

  • We decided to release M2 with known issues. = We have a good handle on some of them, there are others which are unknown b= ut there is no one specific cause of the bugs.

  • We= will run another full QA pass before M3 to try and make sure we are dealin= g with the known bugs.

  • Merging of patches continu= es to be slow as it is proving hard to work out which patches are causing w= hich breakage. The test matrix continues to increase with people being upse= t if their personal favourite set of options breaks yet we can=E2=80=99t ex= pect to test and catch every regression. We=E2=80=99re not sure what to do = about this, the scope of the testing is greater than it ever has been but i= t does seem to be slowing things down.

  • A patch for= performance issues with pseudo when using xattrs have was merged

  • 2.1.1 is currently in QA and is expected to be completed ea= rly next week, this update contains numerous fixes for for a variety of are= as including CVEs, GCC 6.x on Host OS and updated SRC_URIs

    • <= /ul>

    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 releas= e 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 2714 (last week 2744)

    (https://wiki.yoctoproject.org/charts/comb= o.html)


    https://wiki.yoctoproject.o= rg/wiki/Yocto_Project_v2.2_Status

    https://wiki.yoctoproje= ct.org/wiki/Yocto_2.2_Schedule

    https://wiki.yoctoproject.= org/wiki/Yocto_2.2_Features


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


<= /body> --=-qe0GKr7eaYlxSL0K2z1l--