From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f175.google.com (mail-pf1-f175.google.com [209.85.210.175]) by mail.openembedded.org (Postfix) with ESMTP id 73C8D7FE4A for ; Tue, 17 Dec 2019 16:07:33 +0000 (UTC) Received: by mail-pf1-f175.google.com with SMTP id d199so7774897pfd.11 for ; Tue, 17 Dec 2019 08:07:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version:thread-index :content-language; bh=O1HQmVQEXr3jZhpcCFhzC5LA16l1L7IJM6tLfatlNbw=; b=j5DPA+HzjpRZO/gatH6i824quPoJaNEEGLo7/9mJDoIIgh5KXdQ9MyaaXHlWQEHsTr QXZmpQ67Nr0Xu6sjshCbcsq/mOdNfF8HmuRGeEvjA2Ht3gLZCcFU9hBasPstrnsxH+fe 2t66Wt/sTLMY0t2gVB9WKvlRXQ+W9Pi0Irfa8POE+H29TAvCgwEldJbjE4+D6SvuEHT9 +dfcVAN3diHECEX5eAhnN20Y86+rhwOqaQ1gDBHL0rBPBQ79Fw6Q+/2ksKMZl8MliMK6 fb2LvLzDY0PXXqe31vTw/e3rHbP6r7kojnFi0LcEPW/eJUfB9v04uq78BaD8osMSvYQ2 td5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :thread-index:content-language; bh=O1HQmVQEXr3jZhpcCFhzC5LA16l1L7IJM6tLfatlNbw=; b=VQW56gB2h4JiyYhAG9oKkRVpowY5WNO3PVwitGlFNCMlhDAZH39WKZvoVfD6TPLKq8 AAj3FRTtxjj9ZUFbzQg1BuVWapALNcUcCe3KgTASkLT44DZNQ69oLw0q8sSv94L9DS2E qi/axS3ZEgW8Xik4BwV7C09Ac31eXTq4syUaMv3FZwIc6YvfsZuksUl76PT0TMv8MBa1 vE6QhjVuySu9gagYG/tCo6ZjsFTV+DC65ezDVLcU6lXNPVyCL9VMWjRFehaq3vH7B2VH 7mcAymV+BjowAujbFgEBvq3YDJdia9JD0fOnXcZP/Jy7u9brrkmml4nVm87hs5swvls/ an3A== X-Gm-Message-State: APjAAAX03tUZB2+ShlTR7VJbhJnN8W+CvhfXF9fgqotDYE7sJtnyZKsE HBZfh7SBqVpTrHrPU0QGxdc= X-Google-Smtp-Source: APXvYqzQhUJZ5wOipWKza2bo9Mn1BqqpudWGdjHFdHHDpB7MGuGrr7DYKzZAkz75+B2ZTSHJuEPQVw== X-Received: by 2002:a62:5343:: with SMTP id h64mr22402786pfb.171.1576598854265; Tue, 17 Dec 2019 08:07:34 -0800 (PST) Received: from DESKTOP2AADOIF (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id m101sm4045996pje.13.2019.12.17.08.07.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Dec 2019 08:07:33 -0800 (PST) From: To: , Date: Tue, 17 Dec 2019 08:07:33 -0800 Message-ID: <1777d01d5b4f4$17e967d0$47bc3770$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdW08/pp+mDlFgrwSqqOLnt0vJCbAw== Subject: Yocto Project Status WW51'19 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: Tue, 17 Dec 2019 16:07:33 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_1777E_01D5B4B1.09C8BFE0" Content-Language: en-us ------=_NextPart_000_1777E_01D5B4B1.09C8BFE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M2 Next Deadline: YP 3.1 M2 build date 1/20/2020 Next Team Meetings: * Bug Triage meeting Thursday Dec. 19th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Jan. 7th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Dec. 12th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Dec. 17th at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * YP 3.0.1 was released. * YP 3.1 M1 rc8 is in QA * YP 3.1 M1 took a record number of build attempts due to various issues which only appeared during the rc builds. * Despite a successful rc8 build (which still had reproducible build test failures) there are a number of concerns, particularly as there appears to be very slow builds for some 'pathological' hashequiv scenarios. There has been some progress over the weekend on identifying the causes of that and partially addressing them. * There remains a growing set of intermittent autobuilder failures which occur with varying frequencies. We're struggling to find anyone with time/interest to resolve these and they are becoming problematic for reviewing/testing patches and triaging builds. * The TSC is working on LTS plans, productive discussions have been had and a new policy on handling this and stable releases should be available in the coming weeks. * We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjn ABc/edit?usp=sharing * Due to holidays in EU/US, the next status report will be sent in early January (likely 7th). If there is anything critical to report this will happen as needed. YP 3.1 Milestone Dates: * YP 3.1 M1 is in QA * YP 3.1 M1 release date 12/13/2019 * YP 3.1 M2 build date 1/20/2020 * YP 3.1 M2 release date 1/31/2020 * YP 3.1 M3 build date 2/24/2020 * YP 3.1 M3 release date 3/6/2020 * YP 3.1 M4 build date 3/30/2020 * YP 3.1 M4 release date 4/24/2020 Planned upcoming dot releases: * YP 2.7.3 build date 2/10/20 * YP 2.7.3 release date 2/21/20 * YP 3.0.2 build date 2/3/20 * YP 3.0.2 release date 2/14/20 Tracking Metrics: * WDD 2718 (last week 2698) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1410 (last week 1410) * Patches in the Pending State: 564 (40%) [last week 564 (40%)] The Yocto Project's technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status [If anyone has suggestions for other information you'd like to see on this weekly status update, let us know!] Thanks, Stephen K. Jolley Yocto Project Project Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_1777E_01D5B4B1.09C8BFE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M2

Next Deadline: YP = 3.1 M2 build date 1/20/2020

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 3.0.1 was = released.
  • YP 3.1 M1 rc8 is in = QA
  • YP 3.1 M1 took a record number = of build attempts due to various issues which only appeared during the = rc builds.
  • Despite a successful rc8 build = (which still had reproducible build test failures) there are a number of = concerns, particularly as there appears to be very slow builds for some = ‘pathological’ hashequiv scenarios. There has been some = progress over the weekend on identifying the causes of that and = partially addressing them.
  • There remains a growing set of = intermittent autobuilder failures which occur with varying frequencies. = We’re struggling to find anyone with time/interest to resolve = these and they are becoming problematic for reviewing/testing patches = and  triaging builds.
  • The TSC is working on LTS = plans, productive discussions have been had and a new policy on handling = this and stable releases should be available in the coming = weeks.
  • We are continuing to collect = ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-= pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=3Dsharing
  • Due to holidays in EU/US, the = next status report will be sent in early January (likely 7th). If there = is anything critical to report this will happen as = needed.

 

YP 3.1 Milestone = Dates:

  • YP 3.1 M1 is in = QA
  • YP 3.1 M1 release date = 12/13/2019
  • YP 3.1 M2 build date = 1/20/2020
  • YP 3.1 M2 release date = 1/31/2020
  • YP 3.1 M3 build date = 2/24/2020
  • YP 3.1 M3 release date = 3/6/2020
  • YP 3.1 M4 build date  = 3/30/2020
  • YP 3.1 M4 release date  = 4/24/2020

 

Planned upcoming = dot releases:

  • YP 2.7.3 build date  = 2/10/20
  • YP 2.7.3 release date = 2/21/20
  • YP 3.0.2 build date  = 2/3/20
  • YP 3.0.2 release date = 2/14/20

 

Tracking = Metrics:

 

The Yocto = Project’s technical governance is through its Technical Steering = Committee, more information is available at:

https://wiki.yocto= project.org/wiki/TSC

 

The Status reports = are now stored on the wiki at: https://wiki.yocto= project.org/wiki/Weekly_Status

 

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

 

Thanks,

 

Stephen K. Jolley<= o:p>

Yocto = Project Project Manager

(    Cell:         = ;       (208) = 244-4460

* Email:           = ;   sjolley.yp.pm@gmail.com

 

------=_NextPart_000_1777E_01D5B4B1.09C8BFE0-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from yocto-www.yoctoproject.org (yocto-www.yoctoproject.org [140.211.169.56]) by mx.groups.io with SMTP id smtpd.web09.675.1576598857976257480 for ; Tue, 17 Dec 2019 08:07:38 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=j5DPA+Hz; spf=softfail (domain: gmail.com, ip: 140.211.169.56, mailfrom: sjolley.yp.pm@gmail.com) Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 64B7DE0126D; Tue, 17 Dec 2019 08:07:37 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (sjolley.yp.pm[at]gmail.com) * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no * trust * [209.85.210.175 listed in list.dnswl.org] * 0.0 HTML_MESSAGE BODY: HTML included in message * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid Received: from mail-pf1-f175.google.com (mail-pf1-f175.google.com [209.85.210.175]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 18219E0126B for ; Tue, 17 Dec 2019 08:07:34 -0800 (PST) Received: by mail-pf1-f175.google.com with SMTP id q10so940030pfs.6 for ; Tue, 17 Dec 2019 08:07:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version:thread-index :content-language; bh=O1HQmVQEXr3jZhpcCFhzC5LA16l1L7IJM6tLfatlNbw=; b=j5DPA+HzjpRZO/gatH6i824quPoJaNEEGLo7/9mJDoIIgh5KXdQ9MyaaXHlWQEHsTr QXZmpQ67Nr0Xu6sjshCbcsq/mOdNfF8HmuRGeEvjA2Ht3gLZCcFU9hBasPstrnsxH+fe 2t66Wt/sTLMY0t2gVB9WKvlRXQ+W9Pi0Irfa8POE+H29TAvCgwEldJbjE4+D6SvuEHT9 +dfcVAN3diHECEX5eAhnN20Y86+rhwOqaQ1gDBHL0rBPBQ79Fw6Q+/2ksKMZl8MliMK6 fb2LvLzDY0PXXqe31vTw/e3rHbP6r7kojnFi0LcEPW/eJUfB9v04uq78BaD8osMSvYQ2 td5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :thread-index:content-language; bh=O1HQmVQEXr3jZhpcCFhzC5LA16l1L7IJM6tLfatlNbw=; b=DNkl6zVp2kJEcENkIqMB63AnTfQIIqTGMZSgqgcWDfUa0CcIztzpxtcjOIta8zJlSW dakTGe9KZOK2Nem+M9AzSgNzUC4uJ4Cl/uWDknwkTegxHwo40cGgMh3iV2aL5KcKbFmt z2rpY6FMOQo+/l/b5h9f1gzpVU+iMpdFvAQZuGMlKH4+6VVHNn/BiGVrBDSopYxxvJfw DGRFrUY6tg6EDYclB/fC1kANxi6d14XRg1QzcroINugICL7QDVhNA5nvFvJUrcdrL+mY nRNAXU7AuknJz2Hzoa/dHMMDLttDPPRnNtp6F6UEAnxTgU4ueENF2pBtoSAz8+CZ+cFd EqkA== X-Gm-Message-State: APjAAAVcMEz2nQ0xJ4BCR1IZjd0rsbxEA4nSJH7NnoR8LqOZK7Z/6vgr O7doTrRiQE6JT7+yQqLFcgI= X-Google-Smtp-Source: APXvYqzQhUJZ5wOipWKza2bo9Mn1BqqpudWGdjHFdHHDpB7MGuGrr7DYKzZAkz75+B2ZTSHJuEPQVw== X-Received: by 2002:a62:5343:: with SMTP id h64mr22402786pfb.171.1576598854265; Tue, 17 Dec 2019 08:07:34 -0800 (PST) Received: from DESKTOP2AADOIF (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id m101sm4045996pje.13.2019.12.17.08.07.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Dec 2019 08:07:33 -0800 (PST) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW51'19 Date: Tue, 17 Dec 2019 08:07:33 -0800 Message-ID: <1777d01d5b4f4$17e967d0$47bc3770$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdW08/pp+mDlFgrwSqqOLnt0vJCbAw== Content-Type: multipart/alternative; boundary="----=_NextPart_000_1777E_01D5B4B1.09C8BFE0" Content-Language: en-us ------=_NextPart_000_1777E_01D5B4B1.09C8BFE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M2 Next Deadline: YP 3.1 M2 build date 1/20/2020 Next Team Meetings: * Bug Triage meeting Thursday Dec. 19th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Jan. 7th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Dec. 12th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Dec. 17th at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * YP 3.0.1 was released. * YP 3.1 M1 rc8 is in QA * YP 3.1 M1 took a record number of build attempts due to various issues which only appeared during the rc builds. * Despite a successful rc8 build (which still had reproducible build test failures) there are a number of concerns, particularly as there appears to be very slow builds for some 'pathological' hashequiv scenarios. There has been some progress over the weekend on identifying the causes of that and partially addressing them. * There remains a growing set of intermittent autobuilder failures which occur with varying frequencies. We're struggling to find anyone with time/interest to resolve these and they are becoming problematic for reviewing/testing patches and triaging builds. * The TSC is working on LTS plans, productive discussions have been had and a new policy on handling this and stable releases should be available in the coming weeks. * We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjn ABc/edit?usp=sharing * Due to holidays in EU/US, the next status report will be sent in early January (likely 7th). If there is anything critical to report this will happen as needed. YP 3.1 Milestone Dates: * YP 3.1 M1 is in QA * YP 3.1 M1 release date 12/13/2019 * YP 3.1 M2 build date 1/20/2020 * YP 3.1 M2 release date 1/31/2020 * YP 3.1 M3 build date 2/24/2020 * YP 3.1 M3 release date 3/6/2020 * YP 3.1 M4 build date 3/30/2020 * YP 3.1 M4 release date 4/24/2020 Planned upcoming dot releases: * YP 2.7.3 build date 2/10/20 * YP 2.7.3 release date 2/21/20 * YP 3.0.2 build date 2/3/20 * YP 3.0.2 release date 2/14/20 Tracking Metrics: * WDD 2718 (last week 2698) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1410 (last week 1410) * Patches in the Pending State: 564 (40%) [last week 564 (40%)] The Yocto Project's technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status [If anyone has suggestions for other information you'd like to see on this weekly status update, let us know!] Thanks, Stephen K. Jolley Yocto Project Project Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_1777E_01D5B4B1.09C8BFE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M2

Next Deadline: YP = 3.1 M2 build date 1/20/2020

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 3.0.1 was = released.
  • YP 3.1 M1 rc8 is in = QA
  • YP 3.1 M1 took a record number = of build attempts due to various issues which only appeared during the = rc builds.
  • Despite a successful rc8 build = (which still had reproducible build test failures) there are a number of = concerns, particularly as there appears to be very slow builds for some = ‘pathological’ hashequiv scenarios. There has been some = progress over the weekend on identifying the causes of that and = partially addressing them.
  • There remains a growing set of = intermittent autobuilder failures which occur with varying frequencies. = We’re struggling to find anyone with time/interest to resolve = these and they are becoming problematic for reviewing/testing patches = and  triaging builds.
  • The TSC is working on LTS = plans, productive discussions have been had and a new policy on handling = this and stable releases should be available in the coming = weeks.
  • We are continuing to collect = ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-= pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=3Dsharing
  • Due to holidays in EU/US, the = next status report will be sent in early January (likely 7th). If there = is anything critical to report this will happen as = needed.

 

YP 3.1 Milestone = Dates:

  • YP 3.1 M1 is in = QA
  • YP 3.1 M1 release date = 12/13/2019
  • YP 3.1 M2 build date = 1/20/2020
  • YP 3.1 M2 release date = 1/31/2020
  • YP 3.1 M3 build date = 2/24/2020
  • YP 3.1 M3 release date = 3/6/2020
  • YP 3.1 M4 build date  = 3/30/2020
  • YP 3.1 M4 release date  = 4/24/2020

 

Planned upcoming = dot releases:

  • YP 2.7.3 build date  = 2/10/20
  • YP 2.7.3 release date = 2/21/20
  • YP 3.0.2 build date  = 2/3/20
  • YP 3.0.2 release date = 2/14/20

 

Tracking = Metrics:

 

The Yocto = Project’s technical governance is through its Technical Steering = Committee, more information is available at:

https://wiki.yocto= project.org/wiki/TSC

 

The Status reports = are now stored on the wiki at: https://wiki.yocto= project.org/wiki/Weekly_Status

 

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

 

Thanks,

 

Stephen K. Jolley<= o:p>

Yocto = Project Project Manager

(    Cell:         = ;       (208) = 244-4460

* Email:           = ;   sjolley.yp.pm@gmail.com

 

------=_NextPart_000_1777E_01D5B4B1.09C8BFE0--