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 5451EC46467 for ; Tue, 10 Jan 2023 15:44:36 +0000 (UTC) Received: from mail-pj1-f48.google.com (mail-pj1-f48.google.com [209.85.216.48]) by mx.groups.io with SMTP id smtpd.web11.107275.1673365468361642254 for ; Tue, 10 Jan 2023 07:44:28 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=ZGKuahLQ; spf=pass (domain: gmail.com, ip: 209.85.216.48, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pj1-f48.google.com with SMTP id c8-20020a17090a4d0800b00225c3614161so16907397pjg.5 for ; Tue, 10 Jan 2023 07:44:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=thread-index:content-language:mime-version:message-id:date:subject :to:from:from:to:cc:subject:date:message-id:reply-to; bh=DIAx/WP7UADSy3OcZgoZoq/sTdSDwFqgQvKf/Txm998=; b=ZGKuahLQWjoNHwuAx7DPrui4fh9ehWfoEDSBgd/2O9BD6qz5I1Ro5gxdPagn7UfGZf GUz6pZizl9V4KKD62TM23h5NKZ3WuywHxNo8heMz1btjbI2qWtDzsuuJjDwxxM4SZvNS cgDXTbd3Bc77HJEc8fuST0LJVD5+2Gmx5VWOflkjHEIX6znnAtGKRMrM0IhLTFyOXvTv 8EEH05hUn7RLVoBRwqKtsm7couHlHFX4bxr5g9neap110+OvIGrX9GeTwQg4PDbBzJrr 0FZJDXwMoE4AwJbbciji2J+sOuvPFkJF8gjdWHpc+3ldkR2pzyyqXjEOR7Sxx91A3FzT htKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=thread-index:content-language:mime-version:message-id:date:subject :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=DIAx/WP7UADSy3OcZgoZoq/sTdSDwFqgQvKf/Txm998=; b=jM/h5HOktcak4aG0liQo/xixTxW++WueZFqnt3YPgfBGlAaElHAoy95VQS2+RPP1T/ RdilSN9aULsTlYn0lMzObkeT5VOd27hVX7JMjdlL6M7L/39FnjvjAov2HyUGjsD8G/9C d07kpS2tfIceNOXjV8JkZP5QK5H4ANY4gRXanr1Py/RXY7/EWBqnOF8lrYc4Bk3I3cWD WeTFE62EL5/DcRc8iVvnH4Nm+av1XbQzYn6dHpgyEbSuNHnLi0d510B+44yosf/6keJa rDIZp6AEKxX14wXSHszN5SpewLcQ5mp+lJ4aKtYvZCrgSDJ9GtVYVduwTmYI9Iyh/A+z Uj9g== X-Gm-Message-State: AFqh2krbWDsS/xFkO3wt6Vf9LdjFHevHO7/MncsesFYiYRJ6jG138RGU 5RvSl3FycTJNHGT46uCIPy//WLf1XYE= X-Google-Smtp-Source: AMrXdXu/iOFnGpRHJKzdgM1SSRUszO3PhlETKHcNNRljrKzepXDj8C8VVJ64cmbGMQPUJ7jNtv5acw== X-Received: by 2002:a17:90a:7849:b0:226:3a7c:f248 with SMTP id y9-20020a17090a784900b002263a7cf248mr45466445pjl.24.1673365467301; Tue, 10 Jan 2023 07:44:27 -0800 (PST) Received: from skjolley ([2600:1011:a102:bdcb:6496:bc8e:cae:9486]) by smtp.gmail.com with ESMTPSA id u3-20020a17090a890300b00218cd71781csm7373686pjn.51.2023.01.10.07.44.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jan 2023 07:44:26 -0800 (PST) From: To: , Subject: Yocto Project Status 10 January 2023 (WW02) Date: Tue, 10 Jan 2023 08:44:25 -0700 Message-ID: <077001d9250a$6b9667a0$42c336e0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0771_01D924CF.BF398B70" X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AdklCkbIer90+nwkQJePBkedMcY+RQ== 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, 10 Jan 2023 15:44:36 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/175716 This is a multipart message in MIME format. ------=_NextPart_000_0771_01D924CF.BF398B70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 4.2 M2 Next Deadline: 23rd January 2023 YP 4.2 M2 Build Next Team Meetings: * Bug Triage meeting Thursday January 12th 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) * Weekly Project Engineering Sync Tuesday January 10th at 8 am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * YP 4.1.2 is in QA * A large number of package upgrades have merged bringing us up to date with various upstreams. * We have started moving code out of core bbclass files into the function libraries to help reduce parsing memory use, volumes of data transfer and sstate signature data sizes. Help is welcome in developing further patches to improve our function libraries. * The autobuilder controller has been relocated to deal with connectivity issues, we do have some issues to iron out before things are back to normal service. We were unable to upgrade the buildbot version as there were too many other moving pieces. * We are trying to upgrade uninative to include libgcc to deal with pthread_cancel failures. Newer versions of patchelf are proving problematic and appear to be causing segfaults and we're trying to untangle this from other issues. * We have reverted the tune for qemux86-64 back to corei7-64 since we still have v2 hardware that won't work properly with v3 under KVM and similar. * A uninative bug has been exposed by recent bitbake datastore improvements which could cause sstate to be missed/duplicated. * We merged a number of neat rust improvements which add on target cargo support and added automated QA tests for this functionality so we can ensure it continues to work and doesn't regress. Thanks Alex Kiernan, we hope to see more series like this one! * CVE levels in master are becoming worrying again, help would be appreciated to address the open issues. * The autobuilder maintenance window now occurs on Mondays. * We have a growing number of bugs in bugzilla, any help with them is appreciated. 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.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_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 YP 4.2 Milestone Dates: * YP 4.2 M2 build date 2023/01/23 * YP 4.2 M2 Release date 2023/02/03 * YP 4.2 M3 build date 2023/02/20 * YP 4.2 M3 Release date 2023/03/03 * YP 4.2 M4 build date 2023/04/03 * YP 4.2 M4 Release date 2023/04/28 Upcoming dot releases: * YP 4.1.2 built and in QA * YP 4.1.2 Release date 2023/01/20 * YP 3.1.22 build date 2023/01/16 * YP 3.1.22 Release date 2023/01/27 * YP 4.0.7 build date 2023/01/30 * YP 4.0.7 Release date 2023/02/10 * YP 3.1.23 build date 2023/02/13 * YP 3.1.23 Release date 2023/02/24 * YP 4.0.8 build date 2023/02/27 * YP 4.0.8 Release date 2023/03/10 * YP 4.1.3 build date 2023/03/06 * YP 4.1.3 Release date 2023/03/17 * YP 3.1.24 build date 2023/03/20 * YP 3.1.24 Release date 2023/03/31 * YP 4.0.9 build date 2023/04/10 * YP 4.0.9 Release date 2023/04/21 * YP 4.1.4 build date 2023/05/01 * YP 4.1.4 Release date 2023/05/13 * YP 3.1.25 build date 2023/05/08 * YP 3.1.25 Release date 2023/05/19 * YP 4.0.10 build date 2023/05/15 * YP 4.0.10 Release date 2023/05/26 Tracking Metrics: * WDD 2447 (last week 2457) ( https://wiki.yoctoproject.org/charts/combo.html) * OE-Core/Poky Patch Metrics * Total patches found: 1176 (last week 1189) * Patches in the Pending State: 281 (24%) [last week 282 (24%)] * 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_0771_01D924CF.BF398B70 Content-Type: text/html; boundary="----=_NextPart_000_149A_01D91F50.3E508790"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 4.2 M2

Next Deadline: 23rd = January 2023 YP 4.2 M2 Build

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 4.1.2 is in = QA
  • A large number of package = upgrades have merged bringing us up to date with various = upstreams.
  • We have started moving code out = of core bbclass files into the function libraries to help reduce parsing = memory use, volumes of data transfer and sstate signature data sizes. = Help is welcome in developing further patches to improve our function = libraries.
  • The autobuilder controller has = been relocated to deal with connectivity issues, we do have some issues = to iron out before things are back to normal service. We were unable to = upgrade the buildbot version as there were too many other moving = pieces.
  • We are trying to upgrade = uninative to include libgcc to deal with pthread_cancel failures.  = Newer versions of patchelf are proving problematic and appear to be = causing segfaults and we’re trying to untangle this from other = issues.
  • We have reverted the tune for = qemux86-64 back to corei7-64 since we still have v2 hardware that = won’t work properly with v3 under KVM and = similar.
  • A uninative bug has been = exposed by recent bitbake datastore improvements which could cause = sstate to be missed/duplicated.
  • We merged a number of neat rust = improvements which add on target cargo support and added automated QA = tests for this functionality so we can ensure it continues to work and = doesn’t regress. Thanks Alex Kiernan, we hope to see more series = like this one!
  • CVE levels in master are = becoming worrying again, help would be appreciated to address the open = issues.
  • The autobuilder maintenance = window now occurs on Mondays.
  • We have a growing number of = bugs in bugzilla, any help with them is = appreciated.

 

Ways to = contribute:

 

YP 4.2 Milestone = Dates:

  • YP 4.2 M2 build date = 2023/01/23
  • YP 4.2 M2 Release date = 2023/02/03
  • YP 4.2 M3 build date = 2023/02/20
  • YP 4.2 M3 Release date = 2023/03/03
  • YP 4.2 M4 build date = 2023/04/03
  • YP 4.2 M4 Release date = 2023/04/28

 

Upcoming dot = releases:

  • YP 4.1.2 built and in = QA
  • YP 4.1.2 Release date = 2023/01/20
  • YP 3.1.22 build date = 2023/01/16
  • YP 3.1.22 Release date = 2023/01/27
  • YP 4.0.7 build date = 2023/01/30
  • YP 4.0.7 Release date = 2023/02/10
  • YP 3.1.23 build date = 2023/02/13
  • YP 3.1.23 Release date = 2023/02/24
  • YP 4.0.8 build date = 2023/02/27
  • YP 4.0.8 Release date = 2023/03/10
  • YP 4.1.3 build date = 2023/03/06
  • YP 4.1.3 Release date = 2023/03/17
  • YP 3.1.24 build date = 2023/03/20
  • YP 3.1.24 Release date = 2023/03/31
  • YP 4.0.9 build date = 2023/04/10
  • YP 4.0.9 Release date = 2023/04/21
  • YP 4.1.4 build date = 2023/05/01
  • YP 4.1.4 Release date = 2023/05/13
  • YP 3.1.25 build date = 2023/05/08
  • YP 3.1.25 Release date = 2023/05/19
  • YP 4.0.10 build date = 2023/05/15
  • YP 4.0.10 Release date = 2023/05/26

 

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_0771_01D924CF.BF398B70--