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.14833.1598971545267497592 for ; Tue, 01 Sep 2020 07:45:45 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=M/odSCG9; 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 27ABAE0206B; Tue, 1 Sep 2020 07:45:45 -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, URIBL_RED 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.214.196 listed in list.dnswl.org] * 0.0 URIBL_RED Contains an URL listed in the URIBL redlist * [URIs: yoctoproject.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-pl1-f196.google.com (mail-pl1-f196.google.com [209.85.214.196]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id ADA39E0205A for ; Tue, 1 Sep 2020 07:45:42 -0700 (PDT) Received: by mail-pl1-f196.google.com with SMTP id h2so650608plr.0 for ; Tue, 01 Sep 2020 07:45:42 -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:thread-index :content-language; bh=6RTRj5UuQHeCZ0Q+3BcWOIymFh7UJKS1VoJ9htOwU1I=; b=M/odSCG92jkaSIjszTmbpREjKYbOkmLlK4WQg4RbUIqUlAo5hEf3gvizOR1sxAwtMe 8exz+fQbtE+fEJxCcTaIpLXzJh4j3TCuxTUtgbaaxQ42ZBfzsGQYvybjW55y6Dmt9rRI AGUYWxhOZIdTK+6ocDQzUvcHq206o5JW9DsuRi0WCpj+nOb7yswtGkk6BFmxi12CiVmY FbVGmxAPG3VoWrc9IQfz0uaIXKPXbvIgzT59uixjjj3eyTDSTKqKBMrJpTOsGExsKMv8 /7QsJRN3YrSrLvjAnUimKE+Rg6JvaRjWH/RHKkL3ZdzjrEwMteAyY/dZTbISlyv9jvTA +aEw== 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=6RTRj5UuQHeCZ0Q+3BcWOIymFh7UJKS1VoJ9htOwU1I=; b=kf+dycCceREYxxab3WPyju44VDyBNaf38gzdJ9Oa0z7hfCk6F9YtlLmZQJ7i8brU2H v4JX6PxqPNAHPOrBqCunHwGXFYwb/vn6ew8C9xOgWjZp++l9jZDjZc6Ti09yRCiVv3aw LyBdq3jitDVsvfp2MYETF0Hru/QqyPWa9eVGlxquqQgKWMDAYpADb8PBcdZIQXP75qDe BDDTnuv7ON5ohLbsGkmKYuzJKD7PXlNoDh5PKnGSNEHxBEMIeZqNTwJE2qHsyTBn4SuQ xA6HfEf9MU4IuH+lZ41Z98KwNeSRY/Zg2X1U0hvdX6Ru1nlg4Ch8Nb7XPq9WB3Ax1XiP p0xQ== X-Gm-Message-State: AOAM532KJ2Vt0jAIGExl6zEFAPkJCA7xpC1mLDsJCl8yj/g0yHGbjGHH ZLRVMccvVWupWJ/q9KMRZZY= X-Google-Smtp-Source: ABdhPJwvERQUcr7FiNc1xNHBuhTaS4bUZxmVKZCtxsr8PA/cjcdUMsLPrtb2Xrqq3+GDj+Y0B9+UmA== X-Received: by 2002:a17:90b:f84:: with SMTP id ft4mr2003912pjb.174.1598971541900; Tue, 01 Sep 2020 07:45:41 -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 q18sm2292423pfn.106.2020.09.01.07.45.38 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Sep 2020 07:45:40 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW35'20 Date: Tue, 1 Sep 2020 07:45:38 -0700 Message-ID: <076201d6806e$90490230$b0db0690$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdaAbn7DIBuU0YK6QxGHQgY8wtziGw== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0763_01D68033.E3F21970" Content-Language: en-us ------=_NextPart_000_0763_01D68033.E3F21970 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.2 M3 Next Deadline: YP 3.2 M3 Feature Freeze - Now Next Team Meetings: * Bug Triage meeting Thursday Sept. 3rd at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Sept. 1st at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Sept. 8th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * M3 has now closed and we're at feature freeze for 3.2. * There are a number of patches we need for 3.2 which are still being sorted out and M3 will build once that has happened. * Bitbake server startup has been changed to avoid the issues previously discovered. There are some issues with traceback handling/reporting during early init which are being resolved as a result of that and those have open bugs. * The server changes have improved memory resident bitbake but some issues with state tracking still remain so memory resident bitbake will not be the default until 3.3, assuming we can debug those remaining problems by early in 3.3. * There has been work in enabling PRServ to work well with hash equivalence, thanks to Mark for sorting out this long standing work item. We aim to have this in 3.2 but some tests need fixing before it can completely merge. * We will process one last round of recipe upgrades before we build M3. * We were finally able to change the fcommon gcc defaults back to standard, thanks to all who helped make that happen. * The number of autobuilder intermittent bugs has continued to rise unfortunately. You can see the list of failures we're continuing to see by searching for the "AB-INT" tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing. * One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan cements.2FBugs * Globbing support in file:// urls has been removed. YP 3.2 Milestone Dates: * 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.3 build date 2020/9/14 * YP 3.1.3 release date 2020/9/25 Tracking Metrics: * WDD 2436 (last week 2424) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1264 (last week 1273) * Patches in the Pending State: 502 (40%) [last week 502 (39%)] 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_0763_01D68033.E3F21970 Content-Type: text/html; boundary="----=_NextPart_000_0F1D_01D67AB3.FF9C8230"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.2 M3

Next Deadline: YP = 3.2 M3 Feature Freeze - Now

 

Next Team = Meetings:

 

Key = Status/Updates:

  • M3 has now closed and = we’re at feature freeze for 3.2.
  • There are a number of patches = we need for 3.2 which are still being sorted out and M3 will build once = that has happened.
  • Bitbake server startup has been = changed to avoid the issues previously discovered. There are some issues = with traceback handling/reporting during early init which are being = resolved as a result of that and those have open = bugs.
  • The server changes have = improved memory resident bitbake but some issues with state tracking = still remain so memory resident bitbake will not be the default until = 3.3, assuming we can debug those remaining problems by early in = 3.3.
  • There has been work in enabling = PRServ to work well with hash equivalence, thanks to Mark for sorting = out this long standing work item. We aim to have this in 3.2 but some = tests need fixing before it can completely = merge.
  • We will process one last round = of recipe upgrades before we build M3.
  • We were finally able to change = the fcommon gcc defaults back to standard, thanks to all who helped make = that happen.
  • The number of autobuilder = intermittent bugs has continued to rise = unfortunately.

You can see the = list of failures we’re continuing to see by searching for the = “AB-INT” tag in bugzilla: https://bugzilla.y= octoproject.org/buglist.cgi?quicksearch=3DAB-INT

Help with any of = these would be much appreciated, unfortunately it is proving hard to = find anyone interested in helping figure these out and they = significantly hamper our testing.

 

YP 3.2 Milestone = Dates:

  • 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.3 build date = 2020/9/14
  • YP 3.1.3 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_0763_01D68033.E3F21970--