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.web11.12348.1592318858595763854 for ; Tue, 16 Jun 2020 07:47:38 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=enD66a8u; 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 4440AE01C85; Tue, 16 Jun 2020 07:47:38 -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.215.174 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-pg1-f174.google.com (mail-pg1-f174.google.com [209.85.215.174]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id A72AAE01C61 for ; Tue, 16 Jun 2020 07:47:35 -0700 (PDT) Received: by mail-pg1-f174.google.com with SMTP id u128so2437813pgu.13 for ; Tue, 16 Jun 2020 07:47:35 -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=cpVQePc1q626bGuNXlOumQsWXPZVDcMU0CW1njP9CRg=; b=enD66a8uJTc26p8n4A2ZQatX1PiXcGd3AjHqKoK9VKCftOgVdKwWg3918dvJxPeKyG Izv5gO59mkSBh5oKuKyXd6TLTJvwsRfxyQZR4Yh7yC/0G1f4EAGOBuy522NEh1qNwYwp 7cmfNCe1idytwjqwca52LDEzz/KL2lmnH0CfapcLFCuOoydFuVC7esNW1HOc6ziLuWpz aRqfnjCyxqEqTEXANjdJffRuVuR8ZTFZwyHzjVX30yP5EK1LUn7Eqs4SMIREymOEmJse dOMpjc05yJdKTD+O6qn4tYYN4WD2tDjIVlea1Tsx7cijZT731IMnaWCn/shJ8dZ1+RqD d8ag== 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=cpVQePc1q626bGuNXlOumQsWXPZVDcMU0CW1njP9CRg=; b=jCLZ0WvS24pchm4Sd0jZeb2dx5XxVRRWwd6nvdnArbL3/gHqbIclWZIur3a9zYLo9c 5MKICGaXEln50650Chq4EzSvD9ic3y5Qfb8dHDZYRPfACC85eOB+p5AjaxG8tzrCDlyv hDz4HUd8MpyiCLXcNlu4JzCTPFYgV1RyBYOD7Kh2NAypaEyE+ILvfmotR62t8wupKFjf v8w5Wdm27t6LMcyivoM2L3KneeJsmZG7fx2e/9ArQ2cSZR/kQBpHUgcHvaGg2J0G5s3J /giJ3JMJQ+DOY9iK+A1Y6XU+v83WeKYswmGFk9SzNwna3McvsE2SoJmWPrMaXBAE/y/m 5ZAg== X-Gm-Message-State: AOAM531sCrAqDUGQ6Ihysq3fGVDOGSmEO6+D71R5oVC4FsucwXZgVhZ7 e+oElz33I6Kn2yjOaE5Q/1g= X-Google-Smtp-Source: ABdhPJwjue70ZEMagiUBI1ay1LFVq3aXfKbkIQ69Z5ODjPb0DpePQVF1wP3FBAz2ONINVZKTFph2jQ== X-Received: by 2002:aa7:9a5d:: with SMTP id x29mr2330835pfj.65.1592318855003; Tue, 16 Jun 2020 07:47: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 v7sm14618125pfn.147.2020.06.16.07.47.34 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Jun 2020 07:47:34 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW24'20 Date: Tue, 16 Jun 2020 07:47:34 -0700 Message-ID: <18d101d643ed$12d77ab0$38867010$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdZD7O2FiaJBNvaBTZOXKI2EzmLUEA== Content-Type: multipart/alternative; boundary="----=_NextPart_000_18D2_01D643B2.667F0B50" Content-Language: en-us ------=_NextPart_000_18D2_01D643B2.667F0B50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.2 M1 Next Deadline: YP 3.2 M1 build date 2020/6/16 Next Team Meetings: * Bug Triage meeting Thursday June 18th 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 16th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See http://www.twitch.tv/letoatreidesthe2nd Key Status/Updates: * YP 3.1.1 is out from QA and had no defects raised so is likely to be released after review * YP 3.2 M1 will be built as soon as we have a clean build run of the currently queued patches. We've not seen anything else pending critical to M1. * 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. * There was a key fix to the gitsm fetcher which resolved autobuilder regressions, thanks Paul Barker for helping resolve that at short notice. * There were some important improvements to multiconfig this week so that multiconfig task hashes are correctly accounted for and rebuilt as well as BBMASK being handled correctly in individual multiconfigs, thanks Joshua Watt for those improvements. * The biggest concern for both LTS and master right now are the intermittent test failures that keep occurring on the infrastructure, we're struggling to get clean builds of either branch due to these issues. Instability in the upstream distros we run on (which we regularly pull for security updates) are sadly contributing to the issues, seemingly more significantly than usual. * If anyone has thoughts on attracting and recognizing 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 YP 3.2 Milestone Dates: * YP 3.2 M1 build date 2020/6/16 * YP 3.2 M1 Release date 2020/6/26 * 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 should be released shortly. * 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 2515) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1306 (last week 1301) * Patches in the Pending State: 518 (40%) [last week 517 (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_18D2_01D643B2.667F0B50 Content-Type: text/html; boundary="----=_NextPart_000_10C7_01D63E31.B51C2AD0"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.2 M1

Next Deadline: YP = 3.2 M1 build date 2020/6/16

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 3.1.1 is out from QA and had = no defects raised so is likely to be released after = review
  • YP 3.2 M1 will be built as soon = as we have a clean build run of the currently queued patches. = We’ve not seen anything else pending critical to = M1.
  • 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.
  • There was a key fix to the = gitsm fetcher which resolved autobuilder regressions, thanks Paul Barker = for helping resolve that at short notice.
  • There were some important = improvements to multiconfig this week so that multiconfig task hashes = are correctly accounted for and rebuilt as well as BBMASK being handled = correctly in individual multiconfigs, thanks Joshua Watt for those = improvements.
  • The biggest concern for both = LTS and master right now are the intermittent test failures that keep = occurring on the infrastructure, we’re struggling to get clean = builds of either branch due to these issues. Instability in the upstream = distros we run on (which we regularly pull for security updates) are = sadly contributing to the issues, seemingly more significantly than = usual.
  • If anyone has thoughts on = attracting and recognizing 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

 

YP 3.2 Milestone = Dates:

  • YP 3.2 M1 build date = 2020/6/16
  • YP 3.2 M1 Release date = 2020/6/26
  • 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 should be released = shortly.
  • 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_18D2_01D643B2.667F0B50--