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.web10.8619.1592923720067779533 for ; Tue, 23 Jun 2020 07:48:40 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=m0NyG4kR; 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 99698E01CCC; Tue, 23 Jun 2020 07:48:39 -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 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no * trust * [209.85.215.177 listed in list.dnswl.org] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (sjolley.yp.pm[at]gmail.com) * 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-pg1-f177.google.com (mail-pg1-f177.google.com [209.85.215.177]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 6C185E01CBF for ; Tue, 23 Jun 2020 07:48:36 -0700 (PDT) Received: by mail-pg1-f177.google.com with SMTP id r18so9943648pgk.11 for ; Tue, 23 Jun 2020 07:48:36 -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=kwe9NzV4SsqOpVuy0NbduuINoxe4fdJyOZZQ7Cq+y8A=; b=m0NyG4kR7CXVbwHN4EXK/UoiXBIX75TrCF4bg5e+N6qBw/dJu9RpZ10Cz9yiwDyFZO nadgh9jyEWxd/hAdGvHyo/m0meH45ESCiAGC0vdaMqEq3kGoBJRSu6QdWXmKnUS7Mdvy tI72aCYwy/NhkmmlKAxpze6PmKRp0G/D3SjCl1ApYLoYQNzjK3cnkTPhs6spMNqpLEDu cufEXfxo7CmrKiZP15V81asKPh7HPG5q56vynH/OzmBIifdEHhvYjG3ht+MWd1DKJgbw ue9jIHH5emoNBUvCer9ezOwJ7mkOpg7NWrD+SredLNAm+7IgSykHJnTKhb/w0vW71QIT MnxA== 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=kwe9NzV4SsqOpVuy0NbduuINoxe4fdJyOZZQ7Cq+y8A=; b=e8zJw8mOcS9IJW/8qobM8YhsUlw0hU3cgOXuAB7KlDeSVkwLj78P6X36A8taUK9OO3 f1UZFjPxO0KbUEclzocVOIMTzlcWM1M+V/O8WBNsNZlZ4CuT/RJGFkjymQeavZuB6vdI RXtnfqJ+u4xImkOxt3xUAjLBTmLM948+CJftRZqq83Bid+/YF2to8PwarbV+RJbWAxCT x0m6sjh5GWksotGBWQuAwJiZoIww5MOEJMtspGV5X6lbckFT9VMfx2F3bChFXb+NI14P 5McYL99rrv3PTeYDSwhtz+8nD4mtbWPCNCOiSfNnp3RaSFn8Nwo6n+RwcfZ1mkiJDnnM 1HsA== X-Gm-Message-State: AOAM530D3e73qPjdA7VgMGcn+ed4fscuTWAtPHFRsJHADd8oVpIkEk2s ZMV9X2be795fuWoPfnxPIXs= X-Google-Smtp-Source: ABdhPJyKfTjcJAXP7Eqb6om5zXfvMYZUylOJIjOYvLFcHnrt85I7LjIRE5Ehwg1B6UFcSnfSkEpd3g== X-Received: by 2002:a05:6a00:15c7:: with SMTP id o7mr24615088pfu.51.1592923715668; Tue, 23 Jun 2020 07:48:35 -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 m20sm18591675pfk.52.2020.06.23.07.48.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Jun 2020 07:48:35 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW25'20 Date: Tue, 23 Jun 2020 07:48:34 -0700 Message-ID: <067a01d6496d$5f46d9b0$1dd48d10$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdZJbUdP+FsSdrtKSByBV3SeDZdVTw== Content-Type: multipart/alternative; boundary="----=_NextPart_000_067B_01D64932.B2E9AF60" Content-Language: en-us ------=_NextPart_000_067B_01D64932.B2E9AF60 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 June 25th 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 June 23th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See http://www.twitch.tv/letoatreidesthe2nd Key Status/Updates: * YP 3.1.1 was released * YP 3.2 M1 is through QA and awaiting a release decision. The only defects found were two valgrind ptest results so it's likely to release. * 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. * We continue to be concerned about autobuilder stability, we're continuing to see high numbers of intermittent failures (along with instability in upstream repositories which is now also breaking builds). A list of issues was posted to the OE-Core mailing list, there are other older bugs which have also recurred. We have figured out some fixes but help is urgently needed to bring these to a manageable level. * If anyone has thoughts on attracting and recognising project contributors and contributions, we would be interested in ideas and assistance in that area. * There remain a large number of bugs that we'd ideally like to fix in 3.2 M2 but they are "unassigned", there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. 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. * Next week is ELC which is taking place virtually this year and Yocto Project has a presence there. There is also a virtual Yocto Project Developer Day: https://events.linuxfoundation.org/yocto-dev-day-north-america/ * On a positive note, we are looking the closest we've ever been to upstream software versions thanks to AUH and work from Alex in particular, the recent AUH reports have been shorter than ever with low numbers of upgrade failures. YP 3.2 Milestone Dates: * YP 3.2 M1 should be released shortly. * 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.1.1 was released * 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 2545 (last week 2545) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1298 (last week 1306) * Patches in the Pending State: 518 (40%) [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_067B_01D64932.B2E9AF60 Content-Type: text/html; boundary="----=_NextPart_000_18D2_01D643B2.667F0B50"; 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.1.1 was = released
  • YP 3.2 M1 is through QA and = awaiting a release decision. The only defects found were two valgrind = ptest results so it's likely to release.
  • 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.
  • We continue to be concerned = about autobuilder stability, we’re continuing to see high numbers = of intermittent failures (along with instability in upstream = repositories which is now also breaking builds). A list of issues was = posted to the OE-Core mailing list, there are other older bugs which = have also recurred. We have figured out some fixes but help is urgently = needed to bring these to a manageable level.
  • If anyone has thoughts on = attracting and recognising project contributors and contributions, we = would be interested in ideas and assistance in that = area.
  • There remain a large number of = bugs that we’d ideally like to fix in 3.2 M2 but they are = “unassigned”, there is nobody to work on them. If anyone has = time, looking at these bugs would be a great way to help us. 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.
  • Next week is ELC which is = taking place virtually this year and Yocto Project has a presence there. = There is also a virtual Yocto Project Developer Day: = https://events.linuxfoundation.org/yocto-dev-day-= north-america/
  • On a positive note, we are = looking the closest we’ve ever been to upstream software versions = thanks to AUH and work from Alex in particular, the recent AUH reports = have been shorter than ever with low numbers of upgrade = failures.

 

YP 3.2 Milestone = Dates:

  • YP 3.2 M1 should be released = shortly.
  • 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.1.1 was = released
  • 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_067B_01D64932.B2E9AF60--