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.9259.1588690146065912786 for ; Tue, 05 May 2020 07:49:06 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=AxmUl2Eq; 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 B0F0FE01A1B; Tue, 5 May 2020 07:49:05 -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.169 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-f169.google.com (mail-pl1-f169.google.com [209.85.214.169]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 12E7AE01A17 for ; Tue, 5 May 2020 07:49:02 -0700 (PDT) Received: by mail-pl1-f169.google.com with SMTP id x10so914938plr.4 for ; Tue, 05 May 2020 07:49:02 -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=VEhxGs6j6mWHbtmFaTB0u8+41gdTxGxb6YXEP517es8=; b=AxmUl2EqmBHnhUqUnYIEfgifgX2uaMm5GI/0+UAdH1WNzkiHeXAQf9OfPAAECts9tJ EmT/xXkgqxMp90r/6eJapFchGYym4QEGi46vGIDZ9QAWYDDopZhw2r6VjV74sKNyZInl +/4HtDKR8fVnFjd8YK3cKdgXR9rAEcdfHuGSQ7GuXyumhOpeXlQ9LT3dpS3V3ezMFXsW xYKMowXiS47eSdwe/LyqmTW/gmwbEyE/Z9q1eMs09BbjbA2JMAuGt+s/dIUAbWJZDLot DnZaRKxrr+xVHRxXGPJOeCX0rrVD7fzp85hD630nfIvjyj7C3DdQqmu1wvWwHgjnkKXK cahQ== 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=VEhxGs6j6mWHbtmFaTB0u8+41gdTxGxb6YXEP517es8=; b=MLhdfaUgvXwUyHUlK0M4wr7GkIp3zjjJXGktsvPRR1elf4GYHnIC5aSGxk5WdPUZ2M BuVOYzftNEKF9kl5TTogLtdhNJiq+tGg5lxPgLPf5mOhK+aLbuODG2sS9bbpXnWg7v4T s/qCJvmQKz9Xo5Cc1OPSxUhfJjh1sWbPA49JnfR6Y3Hn5KJRGEU/f87lBYZoSCzPKNLK vnK4BIlpNt7VZ+8NkStHFxSXBTXckBOR54dkcwcxIvS3iNrUa5B5wA+u2aMNfZXs+spi /wLAjFdiyTEWO7VfACCMi9lheYAbGSKjlY0Yng26GUGe6f54V37XcekHJpvQ9O2R2PC8 CfBg== X-Gm-Message-State: AGi0PubKum7UVjxee4VfLVivLQZ5hWTc1MkhxH2E6x5p0QQwNPIYB78g ZAPM9UQPZvaUxuj/xPzEL00= X-Google-Smtp-Source: APiQypK0SVNHDIqA7C2y2A/uJyWhV94WkDAZEFTOnUQxW8qg1PG8T4NyPA2InCBOKPHCYuI/3wkAIw== X-Received: by 2002:a17:90a:6f22:: with SMTP id d31mr3579914pjk.14.1588690142335; Tue, 05 May 2020 07:49:02 -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 q21sm1665576pgl.7.2020.05.05.07.49.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 May 2020 07:49:01 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW18'20 Date: Tue, 5 May 2020 07:49:01 -0700 Message-ID: <306d01d622ec$516fb570$f44f2050$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdYi7At9WC6s2cxnT4aPy7r/0LLDHQ== Content-Type: multipart/alternative; boundary="----=_NextPart_000_306E_01D622B1.A512B230" Content-Language: en-us ------=_NextPart_000_306E_01D622B1.A512B230 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 May 7th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday May 5th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday May 12th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See http://www.twitch.tv/letoatreidesthe2nd Key Status/Updates: * We are now merging patches into master, debugging some of the issues has proven problematic but we're making good progress on various deferred upgrades. * In particular there was a further problem with buildtools-extended-tarball which ended up 'corrupting' sstate by over-optimising binaries so they wouldn't run on older CPUs. Fixes for this have merged and we'll need to release a new buildtools tarball. * The 3.1 stable branch has started taking its first rounds of patches, help with review of these would be much appreciated. * A 3.0 stable build is due as soon as the current patches in review are sorted out. * The multilib issue mentioned in previous status reports and on the architecture list is proving tricky, do we make the invasive changes in master-next for master now they appear to work? Backport to dunfell? Or try and come up with a more invasive core bitbake change? * We are aware of some issues with bug trend metrics due to server transitions and are working to resolve those. 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.0.3 build date 2020/5/4 * YP 3.0.3 release date 2020/5/15 * YP 2.7.4 build date 2020/5/18 * YP 2.7.4 release date 2020/5/29 * YP 3.1.1 build date 2020/6/29 * YP 3.1.1 release date 2020/7/10 * 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 2577 (last week 2577) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1353 (last week 1367) * Patches in the Pending State: 536 (40%) [last week 540 (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_306E_01D622B1.A512B230 Content-Type: text/html; boundary="----=_NextPart_000_1143_01D61D31.0249EAD0"; 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:

  • We are now merging patches into = master, debugging some of the issues has proven problematic but = we’re making good progress on various deferred = upgrades.
  • In particular there was a = further problem with buildtools-extended-tarball which ended up = ‘corrupting’ sstate by over-optimising binaries so they = wouldn't run on older CPUs. Fixes for this have merged and we’ll = need to release a new buildtools tarball.
  • The 3.1 stable branch has = started taking its first rounds of patches, help with review of these = would be much appreciated.
  • A 3.0 stable build is due as = soon as the current patches in review are sorted = out.
  • The multilib issue mentioned in = previous status reports and on the architecture list is proving tricky, = do we make the invasive changes in master-next for master now they = appear to work? Backport to dunfell? Or try and come up with a more = invasive core bitbake change?
  • We are aware of some issues = with bug trend metrics due to server transitions and are working to = resolve those.

 

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.0.3 build date = 2020/5/4
  • YP 3.0.3 release date = 2020/5/15
  • YP 2.7.4 build date = 2020/5/18
  • YP 2.7.4 release date = 2020/5/29
  • YP 3.1.1 build date = 2020/6/29
  • YP 3.1.1 release date = 2020/7/10
  • 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_306E_01D622B1.A512B230--