From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id D6D44C433F5 for ; Tue, 11 Jan 2022 15:42:18 +0000 (UTC) Received: from mail-pl1-f174.google.com (mail-pl1-f174.google.com [209.85.214.174]) by mx.groups.io with SMTP id smtpd.web08.9030.1641915737549125823 for ; Tue, 11 Jan 2022 07:42:17 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=PZSUtqYL; spf=pass (domain: gmail.com, ip: 209.85.214.174, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pl1-f174.google.com with SMTP id p14so17773816plf.3 for ; Tue, 11 Jan 2022 07:42:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:subject:date:message-id:mime-version:thread-index :content-language; bh=6RECuKAEdEqPewICv6CbWcxB0zNnRTO1YWgLCNQzsMU=; b=PZSUtqYLtrvJNK+u4Kuo2hozC5UjonSW7Qgd5JJ7elJ8O2aqDhZ9rbwtAD8LUAf+5E eExJ+Dy03OuKx3j+wydAAvfdYJbm0fiQdOx2MDTJqKyUX2eEVsTPU88RyjA0zLSbNXcJ 8tVHfe9jTMZZ8PZM4SA/EOVXbD0kJw0yM6dYXFibgoMLGy2dehILGz9SqK36O2tUNziO yWW7+lCD1jzSsIwjhCK5WdKVC2km7RhhFG655GLYcAn8SBKVslV4kPQikJeryTeJptdO pv7ReI9f5WEo4gUhH13RMW7QafDUr82XzzeX3ZDsO9JNYHoDbC+lV9cZWmSybjIkymRI HTMg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :thread-index:content-language; bh=6RECuKAEdEqPewICv6CbWcxB0zNnRTO1YWgLCNQzsMU=; b=TNIDc4kyIFwcfa274OKp6iVtlb+Iv8BU+8Disg3y9ThdMZV25DGJM49pqNTRSgU9kn jbcJLzjcY9FNhhMvWWu+vejomDk07A6h6YYurAhYy0JEx3fy+x6VMFxVnUIdjp/Pri9G /9hB/s2WqHCvrLzzgFAB+ij05ZQ+19JdOJV4mmlNY31yQnilD4Ji3meR82okTvCmlvM4 U/9BxCAdbTeDuV4Cq51zzbVu2IC9WVauSMrQneiGSPD4NF9EPdYNYttYgNbOItgV7lU6 woXbZjm59IpXt0Cg5Es2nWwnsCV07i91BWLAWUhGZkoyGx12wHVxNEVyEsELgjNJW28U p4zw== X-Gm-Message-State: AOAM533nMALGEoxP9kroccMrlCXAUPfXF42IaikdLiWghRVwou6v49Ky UCmFo9avMgJpxnLpJZ8Ii9Hay2eR5OQ= X-Google-Smtp-Source: ABdhPJxa7QHhlWTGHHA7yXtwC5SpWmdBwWVjLZTGVyqpJe0T5yamgTTOBJp8TWtdfWUxUAvoi0VAVw== X-Received: by 2002:a17:90a:24d:: with SMTP id t13mr3764905pje.68.1641915736633; Tue, 11 Jan 2022 07:42:16 -0800 (PST) Received: from skjolley ([2600:8800:1d92:f800:293c:e2d4:1418:7020]) by smtp.gmail.com with ESMTPSA id r10sm10704057pff.120.2022.01.11.07.42.15 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jan 2022 07:42:16 -0800 (PST) From: To: , Subject: Yocto Project Status WW02`22 Date: Tue, 11 Jan 2022 08:42:15 -0700 Message-ID: <033c01d80701$cf5a1a20$6e0e4e60$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_033D_01D806C7.23026E10" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdgHAbM2bhV3W8daQlWnNNNoNcG+Tg== Content-Language: en-us List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Tue, 11 Jan 2022 15:42:18 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/160414 This is a multipart message in MIME format. ------=_NextPart_000_033D_01D806C7.23026E10 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.5 M2 Next Deadline: 17th Jan. 2022 YP 3.5 M2 build Next Team Meetings: * Bug Triage meeting Thursday Jan. 13th 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) * Monthly Project Meeting Tuesday Feb. 1st at 8 am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Weekly Engineering Sync Tuesday Jan. 11th at 8 am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * YP 3.5 M2 is due to build next week * The autobuilder updates have now mostly stabilized and we are potentially seeing a reduction in intermittent failures. * On modern kernels, we now have the capability within bitbake to disable networking on a per task basis without extra user privileges. There is discussion on the mailing list on how we should enable this and whether it should be on an opt-in or opt-out basis. A second patchset has been proposed for discussion where tasks using the network would need to be explicitly marked as such. * The openssl and webkit reproducibility issues have been fixed. * We have also fixed the reproducibility issues with rust-llvm and golang. With ruby docs disabled, this means we have no reproducibility patch exclusions in OE-Core, thanks Alex Kanavin! * The "oldest kernel" setting used for qemu which is architecture specific is causing issues for allarch packages but the various patches to fix it have also caused other issues and highlighted gaps in our sstate hash tests. There are hopefully now patches ready to merge to fix these issues and the gaps in testing. * CVE issues against master have risen from 7 to 17 so help in addressing those issues would be very welcome. * Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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 Ways to contribute: * There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers * There are bugs that are currently unassigned for YP 3.5. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhan cements.2FBugs * We'd welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main tainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to "Unassigned" soon to help facilitate this. YP 3.5 Milestone Dates: * YP 3.5 M2 build date 2022/01/17 * YP 3.5 M2 Release date 2022/01/28 * YP 3.5 M3 build date 2022/02/21 * YP 3.5 M3 Release date 2022/03/04 * YP 3.5 M4 build date 2022/04/04 * YP 3.5 M4 Release date 2022/04/29 Upcoming dot releases: * YP 3.1.14 build date 2022/01/24 * YP 3.1.14 Release date 2022/02/04 * YP 3.4.2 build date 2022/02/07 * YP 3.4.2 Release date 2022/02/18 * YP 3.3.5 build date 2022/02/14 * YP 3.3.5 Release date 2022/02/25 * YP 3.1.15 build date 2022/03/14 * YP 3.1.15 Release date 2022/03/25 * YP 3.4.3 build date 2022/03/21 * YP 3.4.3 Release date 2022/04/01 * YP 3.3.6 build date 2022/03/28 * YP 3.3.6 Release date 2022/04/08 * YP 3.1.16 build date 2022/04/25 * YP 3.1.16 Release date 2022/05/06 Tracking Metrics: * WDD 2655 (last week 2653) ( https://wiki.yoctoproject.org/charts/combo.html) * OE-Core/Poky Patch Metrics * Total patches found: 1234 (last week 1227) * Patches in the Pending State: 348 (28%) [last week 347 (28%)] 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_033D_01D806C7.23026E10 Content-Type: text/html; boundary="----=_NextPart_000_0DF8_01D80147.FE9282B0"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.5 M2

Next Deadline: 17th = Jan. 2022 YP 3.5 M2 build

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 3.5 M2 is due to build next = week
  • The autobuilder updates have = now mostly stabilized and we are potentially seeing a reduction in = intermittent failures.
  • On modern kernels, we now have = the capability within bitbake to disable networking on a per task basis = without extra user privileges. There is discussion on the mailing list = on how we should enable this and whether it should be on an opt-in or = opt-out basis. A second patchset has been proposed for discussion where = tasks using the network would need to be explicitly marked as = such.
  • The openssl and webkit = reproducibility issues have been fixed.
  • We have also fixed the = reproducibility issues with rust-llvm and golang. With ruby docs = disabled, this means we have no reproducibility patch exclusions in = OE-Core, thanks Alex Kanavin!
  • The “oldest kernel” = setting used for qemu which is architecture specific is causing issues = for allarch packages but the various patches to fix it have also caused = other issues and highlighted gaps in our sstate hash tests. There are = hopefully now patches ready to merge to fix these issues and the gaps in = testing.
  • CVE issues against master have = risen from 7 to 17 so help in addressing those issues would be very = welcome.
  • Intermittent issues continue to = be at record high levels and help is very much welcome in trying to = resolve them. 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?qui= cksearch=3DAB-INT

 

Ways to = contribute:

 

YP 3.5 Milestone = Dates:

  • YP 3.5 M2 build date = 2022/01/17
  • YP 3.5 M2 Release date = 2022/01/28
  • YP 3.5 M3 build date = 2022/02/21
  • YP 3.5 M3 Release date = 2022/03/04
  • YP 3.5 M4 build date = 2022/04/04
  • YP 3.5 M4 Release date = 2022/04/29

 

Upcoming dot = releases:

  • YP 3.1.14 build date = 2022/01/24
  • YP 3.1.14 Release date = 2022/02/04
  • YP 3.4.2 build date = 2022/02/07
  • YP 3.4.2 Release date = 2022/02/18
  • YP 3.3.5 build date = 2022/02/14
  • YP 3.3.5 Release date = 2022/02/25
  • YP 3.1.15 build date = 2022/03/14
  • YP 3.1.15 Release date = 2022/03/25
  • YP 3.4.3 build date = 2022/03/21
  • YP 3.4.3 Release date = 2022/04/01
  • YP 3.3.6 build date = 2022/03/28
  • YP 3.3.6 Release date = 2022/04/08
  • YP 3.1.16 build date = 2022/04/25
  • YP 3.1.16 Release date = 2022/05/06

 

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_033D_01D806C7.23026E10--