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.6555.1583851515368599027 for ; Tue, 10 Mar 2020 07:45:15 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Y3c1IAHj; 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 3FDDBE0179A; Tue, 10 Mar 2020 07:45:15 -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.193 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-f193.google.com (mail-pg1-f193.google.com [209.85.215.193]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 2BE58E01773 for ; Tue, 10 Mar 2020 07:45:13 -0700 (PDT) Received: by mail-pg1-f193.google.com with SMTP id 37so2226891pgm.11 for ; Tue, 10 Mar 2020 07:45:13 -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=RSTOdOCYwDg1acy64REgZteAQLWrG2JCZKfc/ttPgr4=; b=Y3c1IAHj3g/BDJxjjlZnZXesQB4gLDEUKAmCAgaL7H+f93uHVyZtcLE4KiBkRp4bf3 DzdzVW3EM5Y1QhM3EQUcAOf+aOaIGjsYrVT1gHQZnldc3fX8HMaiVLSC1+NsJlyxrQDO q+M8t5gpKB8iy1OmTWtgvv73a+71OFR+OzcGBFjNTuhgJJczIrDDfoPGL1C0JgjBVndL AQMkvZF8L9g6SSYZCZY6ml+zR4oml4fDc/CRen5BFFty3D93QhsaVxBI2RnNHX8w0ThW O2ZryiUqbQf6PTx6SJZ3NLxR+LND01xpYCh84v/ws5J7mqmbvKmpQ/Lh4lHQx2nsXj3k INrw== 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=RSTOdOCYwDg1acy64REgZteAQLWrG2JCZKfc/ttPgr4=; b=SLWBrbLf0rErUQYCeh/oXnqPLY+kosQHDC6zZUH6OMXc7+SovcrcZxhz4BkBFACJPA FRV3MbQU/Qv7vwi9fYq2Vd2f1wCWAyQa/hN8Ui8xzdOx5LIX+InoLmTJW/32ImCvmLwk zNF5R1pFlsi+0uzS4xyVOO8u9ddePa8bgQkYK1WHkL/tqZZQioTV5rZEV1cwDYF1ciNy Q6zw0KnHemI6exo5LnC+Zk6vDI2gWDGk1uriMnp87lrDGz8VSnqtnL1/00mP5e91LicF Hc9T+8q2lDCxKER+XhgdmM6EEafnrHQgBt+PL80tM2g5PrkBRydbfZ0Zz+BAizn+LXWA F8Qw== X-Gm-Message-State: ANhLgQ1/SvG/P/KQ9a8w0Vgh+KDV7XEBdPlgq1EGVNeMUpZ/BmX1R4fd NSS1xQ3FAKTNUDfLUuWT8CI= X-Google-Smtp-Source: ADFU+vvEJXi6XiVHu4fDMmNLZb2J0MB2PdIKBvii1b89KmDV38c+0dCPFRuK3ykgTB0remUcOq0M1A== X-Received: by 2002:a63:a65:: with SMTP id z37mr2564462pgk.31.1583851512638; Tue, 10 Mar 2020 07:45:12 -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 d24sm50106784pfq.75.2020.03.10.07.45.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Mar 2020 07:45:12 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW10'20 Date: Tue, 10 Mar 2020 07:45:11 -0700 Message-ID: <00d301d5f6ea$811bf190$8353d4b0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdX26bm7wN0HgPqkQgS7CXdximMj6w== Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D4_01D5F6AF.D4C15F50" Content-Language: en-us ------=_NextPart_000_00D4_01D5F6AF.D4C15F50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M3 - At Feature Freeze, build pending Next Deadline: YP 3.1 M3 build date 2/24/2020 Next Team Meetings: * Bug Triage meeting Thursday Mar. 12th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Apr. 7th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Mar. 10th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See http://www.twitch.tv/letoatreidesthe2nd Key Status/Updates: * YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/ * We are now past M3 feature freeze. The blocking issues continue to reduce, thanks to everyone who has contributed fixes. The remaining issues are: * continued minor bugs with buildtools tarball integration * coreutils ptest blocked on reproducibility issues with gcc-plugins * SystemExit() intermittent selftest failure * pseudo sysroot high priority bug * There are significant changes proposed to bitbake's logging structure to address concerns raised by hashequiv changes. These are currently in testing and are likely to become part of M3 given the timing, wider review is welcome. * Recipe upgrades are now unlikely to be merged into 3.1 as we focus on stabilizing and bug fixing for the release * Autobuilder build results continue to be a concern as we're not getting green builds very often due to multiple varied issues. YP 3.1 Milestone Dates: * YP 3.1 M3 build date 2/24/2020 * YP 3.1 M3 release date 3/6/2020 * YP 3.1 M4 build date 3/30/2020 * YP 3.1 M4 release date 4/24/2020 Planned upcoming dot releases: * YP 3.0.3 build date 5/4/2020 * YP 3.0.3 release date 5/15/2020 * YP 2.7.4 build date 5/18/2020 * YP 2.7.4 release date 5/29/2020 Tracking Metrics: * WDD 2703 (last week 2720) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1354 (last week 1346) * Patches in the Pending State: 541 (40%) [last week 539 (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_00D4_01D5F6AF.D4C15F50 Content-Type: text/html; boundary="----=_NextPart_000_107D_01D5F131.ADD38630"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M3 - At Feature Freeze, build = pending

Next Deadline: YP = 3.1 M3 build date 2/24/2020

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 3.1 has been announced as an = LTS release: https://www.yoctoproject.org/yocto-project-long-t= erm-support-announced/
  • We are now past M3 feature = freeze. The blocking issues continue to reduce, thanks to everyone who = has contributed fixes. The remaining issues = are:
    • continued minor bugs with = buildtools tarball integration
    • coreutils ptest blocked on = reproducibility issues with gcc-plugins
    • SystemExit() intermittent = selftest failure
    • pseudo sysroot high priority = bug
  • There are significant changes = proposed to bitbake’s logging structure to address concerns raised = by hashequiv changes. These are currently in testing and are likely to = become part of M3 given the timing, wider review is = welcome.
  • Recipe upgrades are now = unlikely to be merged into 3.1 as we focus on stabilizing and bug fixing = for the release
  • Autobuilder build results = continue to be a concern as we’re not getting green builds very = often due to multiple varied issues.

 

YP 3.1 Milestone = Dates:

  • YP 3.1 M3 build date = 2/24/2020
  • YP 3.1 M3 release date = 3/6/2020
  • YP 3.1 M4 build date  = 3/30/2020
  • YP 3.1 M4 release date  = 4/24/2020

 

Planned upcoming = dot releases:

  • YP 3.0.3 build date  = 5/4/2020
  • YP 3.0.3 release date = 5/15/2020
  • YP 2.7.4 build date  = 5/18/2020
  • YP 2.7.4 release date = 5/29/2020

 

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_00D4_01D5F6AF.D4C15F50--