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 21B5BC77B7A for ; Tue, 6 Jun 2023 14:43:50 +0000 (UTC) Received: from mail-pj1-f54.google.com (mail-pj1-f54.google.com [209.85.216.54]) by mx.groups.io with SMTP id smtpd.web11.278.1686062622970271128 for ; Tue, 06 Jun 2023 07:43:43 -0700 Authentication-Results: mx.groups.io; dkim=fail reason="signature has expired" header.i=@gmail.com header.s=20221208 header.b=CZTlI34s; spf=pass (domain: gmail.com, ip: 209.85.216.54, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pj1-f54.google.com with SMTP id 98e67ed59e1d1-2568caabfbfso3032130a91.3 for ; Tue, 06 Jun 2023 07:43:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686062622; x=1688654622; h=content-language:thread-index:mime-version:message-id:date:subject :to:from:from:to:cc:subject:date:message-id:reply-to; bh=QLgn5jQdEsV8aFxbYsOXA+sy4V6qgN0TALByftmdmNo=; b=CZTlI34s7TwZ+hv2nx3TBKsan3eEG6wGBPtnAcvAHbhIpIqOWk3fplit0vAisZfIRU aa92XiKh8mz9ONtZOSVZ7UxFidMcVa5JX/G4jlJ0TxEDc4sN+OWgHin0t+oz81eQrLeC 6MtwwTkGNvbdfJA/NqvOBzUIIDqwUQ0mKrZkLO/aB4yooF6fER42YTK68SoUQD5be/gK wpeWkQeKfntHiO87VJXXTj91djwMhhypVg+WikoD44tEaSpMJQtIK/EKxtDEGzpflYSU b8CkAxD5JmvETPH7A6mgtc0vjcHE6ZuD4BuO+omGlJyS5Lc0ylxNvfLeVuYCjJgJ6SgN 3rgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686062622; x=1688654622; h=content-language:thread-index:mime-version:message-id:date:subject :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QLgn5jQdEsV8aFxbYsOXA+sy4V6qgN0TALByftmdmNo=; b=SBLy3nHM/0M+3h9MbItxnav4BUTBz9R3hOtdackJVL1F/iDxjjemI4UBqiTOWEWyj7 WO8PnklIRACRjcZTQVm1pu7KhCd1v/54nCaz2/Rms0I1PaATwJVM5fE08J1quhEfQCwy qQ0eEt7nJOoa9kEYeV+NIKDxsXfsTiyP0ETEF2CW4ErkcCqrx2vRDMNki9DUQmel4D1Y 8DHE4368Q6poybrULmpW87vW4qpcWvrg65egP6jB4/0D+nOufWiv7kkcUqzsu73TQzjf wmO1uiMwiamdxizU06VrtUnfybVQT7R4mlRsKmVBOOvH3cYJYZ8wSLrypXzD+Ksx8zCe pqOQ== X-Gm-Message-State: AC+VfDzqhNYhYweTBc/dAFT32rEoaUGomLjan2prkkF4mvM8mLJZV48B O376MN3gbWgsGCzJwP8rMdpFT5K5/aY= X-Google-Smtp-Source: ACHHUZ5VFCnoKJFwvw6kjcq3jrU5csByG1d62EqVNSy0vLh93Jsw3M6hQQynJH4ObwTwVGX8J/7DFA== X-Received: by 2002:a17:90a:1a05:b0:258:d910:619d with SMTP id 5-20020a17090a1a0500b00258d910619dmr962536pjk.14.1686062621677; Tue, 06 Jun 2023 07:43:41 -0700 (PDT) Received: from skjolley ([2600:1011:a122:34d2:28e7:9ea4:5bbb:7068]) by smtp.gmail.com with ESMTPSA id 6-20020a17090a08c600b00255d3bd5ce5sm9484865pjn.45.2023.06.06.07.43.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jun 2023 07:43:41 -0700 (PDT) From: To: , Subject: Yocto Project Status 6 June 2023 (WW23) Date: Tue, 6 Jun 2023 07:43:40 -0700 Message-ID: <080901d99885$496ef0e0$dc4cd2a0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_080A_01D9984A.9D14FAE0" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdmYhR4KqLhQR97/Rg+fa9agc3frVg== 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, 06 Jun 2023 14:43:50 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/182443 This is a multipart message in MIME format. ------=_NextPart_000_080A_01D9984A.9D14FAE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 4.3 M1 Next Deadline: 5th June 2023 YP 4.3 M1 build date Next Team Meetings: * Bug Triage meeting Thursday June 8th 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) * Weekly Project Engineering Sync Tuesday June 6th at 8 am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * YP 4.3 M1 is due to build this week * The remaining issue with SPDX manifest generation on the autobuilder should have been identified and fixed so we plan to enable the create_spdx class by default in poky assuming a successful test build. * The recent 6.1 kernel stable updates appear to be causing a couple of different intermittent autobuilder issues. We're working to try and get to the bottom of that, we're hoping further updates to the 6.1 series may pull in fixes for the regressions. * Patch merging has been slow this week as we struggled to bisect failures down to the problematic commits (potentially the sqlite version bump). * We continue to see problematic intermittent failures on the autobuilder. We're struggling to make progress against these and they are feeling overwhelming. We're open to ideas on how we might try and address them. Experience shows that if left unresolved/ignored, people do end up hitting them in real world usage or during testing of their own products. * There are a number of patches still queued in master-next as it is unclear whether they're ready for various reasons. For bandwidth reasons these will likely be deferred to M2, people are just stretched too thinly to do otherwise, frustrating as it is. * Big thanks to Ross for helping look at the high number of CVE issues open against master. Ways to contribute: * As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: patchtest, layerindex, devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components! * 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 4.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_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. * Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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 us resolve CVE issues: CVE metrics * We have a growing number of bugs in bugzilla, any help with them is appreciated. YP 4.3 Milestone Dates: * YP 4.3 M1 build date 2023/06/05 * YP 4.3 M1 Release date 2023/06/16 * YP 4.3 M2 build date 2023/07/17 * YP 4.3 M2 Release date 2023/07/28 * YP 4.3 M3 build date 2023/08/28 * YP 4.3 M3 Release date 2023/09/08 * YP 4.3 M4 build date 2023/10/02 * YP 4.3 M4 Release date 2023/10/27 Upcoming dot releases: * YP 3.1.26 build date 2023/06/19 * YP 3.1.26 Release date 2023/06/30 * YP 4.0.11 build date 2023/06/26 * YP 4.0.11 Release date 2023/07/07 * YP 4.2.2 build date 2023/07/10 * YP 4.2.2 Release date 2023/07/21 * YP 3.1.27 build date 2023/07/31 * YP 3.1.27 Release date 2023/08/11 * YP 4.0.12 build date 2023/08/07 * YP 4.0.12 Release date 2023/08/18 * YP 4.2.3 build date 2023/08/28 * YP 4.2.3 Release date 2023/09/08 * YP 3.1.28 build date 2023/09/18 * YP 3.1.28 Release date 2023/09/29 * YP 4.0.13 build date 2023/09/25 * YP 4.0.13 Release date 2023/10/06 * YP 3.1.29 build date 2023/10/30 * YP 3.1.29 Release date 2023/11/10 * YP 4.0.14 build date 2023/11/06 * YP 4.0.14 Release date 2023/11/17 * YP 4.2.4 build date 2023/11/13 * YP 4.2.4 Release date 2023/11/24 * YP 3.1.30 build date 2023/12/11 * YP 3.1.30 Release date 2023/12/22 * YP 4.0.15 build date 2023/12/18 * YP 4.0.15 Release date 2023/12/29 Tracking Metrics: * WDD 2527 (last week 2522) ( https://wiki.yoctoproject.org/charts/combo.html) * OE-Core/Poky Patch Metrics * Total patches found: 1162 (last week 1160) * Patches in the Pending State: 271 (23%) [last week 272 (23%)] * https://autobuilder.yocto.io/pub/non-release/patchmetrics/ 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_080A_01D9984A.9D14FAE0 Content-Type: text/html; boundary="----=_NextPart_000_09F3_01D992CA.5875BB20"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 4.3 M1

Next Deadline: 5th = June 2023 YP 4.3 M1 build date

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 4.3 M1 is due to build this = week
  • The remaining issue with SPDX = manifest generation on the autobuilder should have been identified and = fixed so we plan to enable the create_spdx class by default in poky = assuming a successful test build.
  • The recent 6.1 kernel stable = updates appear to be causing a couple of different intermittent = autobuilder issues. We’re working to try and get to the bottom of = that, we’re hoping further updates to the 6.1 series may pull in = fixes for the regressions.
  • Patch merging has been slow = this week as we struggled to bisect failures down to the problematic = commits (potentially the sqlite version bump).
  • We continue to see problematic = intermittent failures on the autobuilder. We’re struggling to make = progress against these and they are feeling overwhelming. We’re = open to ideas on how we might try and address them. Experience shows = that if left unresolved/ignored, people do end up hitting them in real = world usage or during testing of their own = products.
  • There are a number of patches = still queued in master-next as it is unclear whether they’re ready = for various reasons. For bandwidth reasons these will likely be deferred = to M2, people are just stretched too thinly to do otherwise, frustrating = as it is.
  • Big thanks to Ross for helping = look at the high number of CVE issues open against = master.

 

Ways to = contribute:

 

YP 4.3 Milestone = Dates:

  • YP 4.3 M1 build date  = 2023/06/05
  • YP 4.3 M1 Release date = 2023/06/16
  • YP 4.3 M2 build date  = 2023/07/17
  • YP 4.3 M2 Release date = 2023/07/28
  • YP 4.3 M3 build date  = 2023/08/28
  • YP 4.3 M3 Release date = 2023/09/08
  • YP 4.3 M4 build date  = 2023/10/02
  • YP 4.3 M4 Release date = 2023/10/27

 

Upcoming dot = releases:

  • YP 3.1.26 build date = 2023/06/19
  • YP 3.1.26 Release date = 2023/06/30
  • YP 4.0.11 build date = 2023/06/26
  • YP 4.0.11 Release date = 2023/07/07
  • YP 4.2.2 build date = 2023/07/10
  • YP 4.2.2 Release date = 2023/07/21 
  • YP 3.1.27 build date = 2023/07/31
  • YP 3.1.27 Release date = 2023/08/11
  • YP 4.0.12 build date = 2023/08/07
  • YP 4.0.12 Release date = 2023/08/18
  • YP 4.2.3 build date = 2023/08/28
  • YP 4.2.3 Release date = 2023/09/08
  • YP 3.1.28 build date = 2023/09/18
  • YP 3.1.28 Release date = 2023/09/29
  • YP 4.0.13 build date = 2023/09/25
  • YP 4.0.13 Release date = 2023/10/06
  • YP 3.1.29 build date = 2023/10/30
  • YP 3.1.29 Release date = 2023/11/10
  • YP 4.0.14 build date = 2023/11/06
  • YP 4.0.14 Release date = 2023/11/17
  • YP 4.2.4 build date = 2023/11/13
  • YP 4.2.4 Release date = 2023/11/24
  • YP 3.1.30 build date = 2023/12/11
  • YP 3.1.30 Release date = 2023/12/22
  • YP 4.0.15 build date = 2023/12/18
  • YP 4.0.15 Release date = 2023/12/29

 

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_080A_01D9984A.9D14FAE0--