From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 7F40AE0104E; Fri, 19 Aug 2016 08:23:12 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [134.134.136.65 listed in list.dnswl.org] Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id B3C07E01048 for ; Fri, 19 Aug 2016 08:23:07 -0700 (PDT) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP; 19 Aug 2016 08:23:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,544,1464678000"; d="scan'208,217";a="750984466" Received: from swold-mobl2.amr.corp.intel.com ([10.254.25.136]) by FMSMGA003.fm.intel.com with ESMTP; 19 Aug 2016 08:23:06 -0700 Message-ID: <1471620185.6975.191.camel@linux.intel.com> From: Saul Wold To: yocto@yoctoproject.org Date: Fri, 19 Aug 2016 08:23:05 -0700 X-Mailer: Evolution 3.20.5 (3.20.5-1.fc24) Mime-Version: 1.0 Subject: Yocto Project Status WW34 X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2016 15:23:12 -0000 Content-Type: multipart/alternative; boundary="=-v1blmPeIfJ+aoZpJ/6ni" --=-v1blmPeIfJ+aoZpJ/6ni 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: Juro -> Anibal https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * We’re drawing close to the M3 deadline and feature freeze for 2.2. There is still a significant number of features outstanding with several looking to be at risk at this point. * The bitbake multi-config build series has now merged. * We’ve re-enabled prelink on x86/mips. ppc/arm was disabled whilst we investigated test failures but will likely be enabled since the issues are looking to be a binutils bug. * We upgraded to gcc 6.2rc1 (we will track 6.2 through to our release) * Uninative 1.3 was released to deal with some locale problems. This will need to be backported to krogoth as a 1.0.1 release of uninative. * Current master is going to go through a full QA pass before M3 to try and make sure we are dealing with all the known bugs. * We are starting to see significant ‘random’ autobuilder failures again: * Mips machine ‘failure to start’ despite booting the kernel: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10136 * Systemd logging failure: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10128 * Unknown ppc failure: https://autobuilder.yoctoproject.org/main/builders/nightly-ppc/builds/910/steps/Running%20Sanity%20Tests/logs/stdio * Uvesa timeout issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=8245 * Busybox parallel make race: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10116 We need to get to grips with these as a matter of urgency as they do keep recurring and several occurred during our QA build, sadly. I am getting quite concerned about these. * 2.1.1 has been released, finally! * We will be moving to the 4.7 kernel before M3 closes, and evaluating a move to 4.8 in mid-September.  We will be keeping both the 4.1 (as LTSI) and 4.4 (as LTS) kernels.  GregKH has announced that 4.9 will be the next LTS for a Dec/Jan release, therefore our 4.7 (or 4.8) will be short lived kernels. 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 2706  (last week 2712) (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!] --=-v1blmPeIfJ+aoZpJ/6ni Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable



Current Dev Posit= ion: YP 2.2 M3

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


SWAT tea= m rotation: Juro -> Anibal

= https://wiki.yoctopr= oject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

We need to get to grips with these as a matter of urgency as= they do keep recurring and several occurred during our QA build, sadly. I = am getting quite concerned about these.


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 releas= e 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:

(https://wiki.yoctoproject.org/charts/combo.html)


Key Status Links f= or YP:

https://wiki.yoctoproject.org/wiki/Yocto_Projec= t_v2.2_Status

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

https://wiki.yoctoproject.org/wiki/Yocto_2.2_F= eatures


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


--=-v1blmPeIfJ+aoZpJ/6ni--