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.web12.16764.1593528770430984302 for ; Tue, 30 Jun 2020 07:52:50 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=F59cdXDF; 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 0D6EEE01D25; Tue, 30 Jun 2020 07:52:50 -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=-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.216.44 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-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3CB0EE01D25 for ; Tue, 30 Jun 2020 07:52:47 -0700 (PDT) Received: by mail-pj1-f44.google.com with SMTP id o22so4517933pjw.2 for ; Tue, 30 Jun 2020 07:52:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version:content-language :thread-index; bh=6FO25NeqIqWIk0LlxWqfkcHgqs5LATRMCP8S+LhGufI=; b=F59cdXDFRI6iqTR1Iz4aC9azEOIaVSsVjuq7IhgEhiOLRvEpYEE2YiuU1bqNUZY30h PD/ID4WA3VxEykhCFrMaPMclDUltwLXZ8yCqOh1tY9x0PEjuxW2xe+vRvnsx2l/h+6A0 tU46r6eU09MvZXCnmlOkIq3mQHLBzmdJ/65E97F570YcjwlByVHHRwjJ16PJ8dYpjwBX Bv307JITWvI3P/KYVZpQKtHSxh6JNpdkZBrmBPkNBht5uexooh7nxcSt1IfBY6drXQj1 MiI8Uq2QhUEALATkrBO2jzoQg95yyZMjdJ578zC2lKK2fbB9xWKtDAUjAl0aNm0bjBuQ K2rg== 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 :content-language:thread-index; bh=6FO25NeqIqWIk0LlxWqfkcHgqs5LATRMCP8S+LhGufI=; b=efmxwvwwx/KPKRie8RvjaYImveeSCmFSTIKBi44ZkdE5bdIBl/1/bWKekOjtQOP8Xa Ql/bMan+TMpLeOvPjpKY0JZWpG4CINT658NsrIQez91kEoS2NfwASk1J0zqUbLSVGZAO tkRqNujYf8s+pq74DOLSuGqW6uV2L1Ym8GIPUKGLWZuqzA1Tq2PvwdM7QczGFqepIEBc P/96xuEcXc1IZU2x1N2e6M7MKeXD3FNGiVRYrsXMLPjNr9UCyAsHiZjXcnZ2dyz+lZAl WVqe+J9XPFis4yrqB9hfffDNoZzQiUSRll+PcSnolRq0HfsiNnn+WbnhyN19Pa+fPfKh Gq1g== X-Gm-Message-State: AOAM532cqqVMtTmg0Xvft9Bek+4j6+dtMgD7zvXUljg/gC9VwecXC+WP 8A/LqfoFWfK95qQVGF82g4g= X-Google-Smtp-Source: ABdhPJyEuy0/yxxeR0GozN1azhtJcFUF6kp9BV3E1xHe5JmzDYqM7o7sLTNI3Q9NmQYxw588V6DBGg== X-Received: by 2002:a17:90a:f282:: with SMTP id fs2mr20923228pjb.132.1593528766654; Tue, 30 Jun 2020 07:52:46 -0700 (PDT) Received: from skjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id mw5sm2889532pjb.27.2020.06.30.07.52.45 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jun 2020 07:52:46 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW26'20 Date: Tue, 30 Jun 2020 07:52:46 -0700 Message-ID: <240c01d64eee$1e6ab160$5b401420$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdZO7h3UpvRfzJLmQiqxAHg6rgz3sA== Content-Type: multipart/alternative; boundary="----=_NextPart_000_240D_01D64EB3.72113090" Content-Language: en-us ------=_NextPart_000_240D_01D64EB3.72113090 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.2 M2 Next Deadline: YP 3.2 M2 build date 2020/7/27 Next Team Meetings: * Bug Triage meeting Thursday July 2nd at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday July 7th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday July 14th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * YP 3.2 M1 was released. * We've updated to a new version of the buildtools tarball for master and dunfell * We continue to be concerned about autobuilder stability, we're continuing to see high numbers of intermittent failures. You can see the list of failures we're seeing by searching for the "AB-INT" tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT Help is urgently needed to bring these to a manageable level. * We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard. * If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area. * It is ELC this week, please stop by the booth and/or ELC #2-track-yocto-project slack channel and say hi. There are still places available on our virtual Developer Day: https://events.linuxfoundation.org/yocto-dev-day-north-america/ * Another way to help the project is to help us with bugs that are currently unassigned but ideally needed during 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan cements.2FBugs * We're pleased to announce we have a new manual in the Yocto Project documentation 'bookshelf' which covers the project's testing processes and infrastructure including the autobuilder and resulttool. A work-in-progress version of this can be viewed here: https://www.yoctoproject.org/docs/docs_temp/test-manual/test-manual.html. So far, it contains basic information in key areas, we're happy to take feedback on areas that are missing or need more information and/or take contributions to further extend this work. YP 3.2 Milestone Dates: * YP 3.2 M1 is released. * YP 3.2 M2 build date 2020/7/27 * YP 3.2 M2 Release date 2020/8/7 * YP 3.2 M3 build date 2020/8/31 * YP 3.2 M3 Release date 2020/9/11 * YP 3.2 M4 build date 2020/10/5 * YP 3.2 M4 Release date 2020/10/30 Planned upcoming dot releases: * YP 3.0.4 build date 2020/8/10 * YP 3.0.4 release date 2020/8/21 * YP 3.1.2 build date 2020/9/14 * YP 3.1.2 release date 2020/9/25 Tracking Metrics: * WDD 2470 (last week 2545) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1272 (last week 1298) * Patches in the Pending State: 498 (39%) [last week 518 (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 Program Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_240D_01D64EB3.72113090 Content-Type: text/html; boundary="----=_NextPart_000_067B_01D64932.B2E9AF60"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.2 M2

Next Deadline: YP = 3.2 M2 build date 2020/7/27

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 3.2 M1 was = released.
  • We’ve updated to a new = version of the buildtools tarball for master and = dunfell
  • We continue to be concerned = about autobuilder stability, we’re continuing to see high numbers = of intermittent failures. You can see the list of failures we’re = seeing by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?qui= cksearch=3DAB-INT

Help is urgently = needed to bring these to a manageable level.

  • We are struggling with = maintainers for some key components of the system/infrastructure such as = devtool, wic, buildhistory and patchwork/patchtest. If anyone can help = in these areas please contact Richard.
  • If anyone has thoughts on = attracting and recognising project contributors and contributions, we = would be interested in ideas and assistance in that = area.
  • It is ELC this week, please = stop by the booth and/or ELC #2-track-yocto-project slack channel and = say hi. There are still places available on our virtual Developer Day: = = https://events.linuxfoundation.org/yocto-dev-day-= north-america/
  • Another way to help the project = is to help us with bugs that are currently unassigned but ideally needed = during 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Med= ium.2B_3.2_Unassigned_Enhancements.2FBugs
  • We’re pleased to announce = we have a new manual in the Yocto Project documentation = ‘bookshelf’ which covers the project’s testing = processes and infrastructure including the autobuilder and resulttool. A = work-in-progress version of this can be viewed here: https://www.yoctoproject.org/docs/docs_temp/test-= manual/test-manual.html. So far, it contains basic = information in key areas, we’re happy to take feedback on areas = that are missing or need more information and/or take contributions to = further extend this work.

 

YP 3.2 Milestone = Dates:

  • YP 3.2 M1 is = released.
  • YP 3.2 M2 build date = 2020/7/27
  • YP 3.2 M2 Release date = 2020/8/7
  • YP 3.2 M3 build date = 2020/8/31
  • YP 3.2 M3 Release date = 2020/9/11
  • YP 3.2 M4 build date = 2020/10/5
  • YP 3.2 M4 Release date = 2020/10/30

 

Planned upcoming = dot releases:

  • YP 3.0.4 build date = 2020/8/10
  • YP 3.0.4 release date = 2020/8/21
  • YP 3.1.2 build date = 2020/9/14
  • YP 3.1.2 release date = 2020/9/25

 

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 Program Manager

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

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

 

------=_NextPart_000_240D_01D64EB3.72113090--