From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pf1-f180.google.com (mail-pf1-f180.google.com [209.85.210.180]) by mx.groups.io with SMTP id smtpd.web10.15328.1598366857947688203 for ; Tue, 25 Aug 2020 07:47:38 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Q3av53//; spf=pass (domain: gmail.com, ip: 209.85.210.180, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pf1-f180.google.com with SMTP id k18so7524498pfp.7 for ; Tue, 25 Aug 2020 07:47:37 -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=rx4U9fN4xre7YYlod61GWrlYAxrtbJOMpZmAzO3f7MY=; b=Q3av53//RHei9J2n5VMZ1vkhBGVV6EkpVuuVxxCbk6Ib5cAAkYD0ks34XBgpOPaR4O F9bDE/3LIZemY7GSZJ9arcMtV/72fz2ptvon71LVAeGrc/EkbciMpuzVxF1Yl5G1QWKw jRdaNSCJmMCStR8jGTPEksTJlzOhp3gys0YIyT1gFwp1uXzEDnti8ROgxNIKlLOBel/4 dgb9MIaZ6QYAUZgCrHTCKF6z0+TqJToAm8eDjsZ8KiAtRjO0JXq2OqLdPPo/Ni1H2Gvw B+Ob6K/PraDjLsPFe5Oc4N7ROgRWUz63XKxZlBfTXduHWdu8UDDdvPXkQ2MZkNa94qBn H8Ug== 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=rx4U9fN4xre7YYlod61GWrlYAxrtbJOMpZmAzO3f7MY=; b=lTaWOH8xUE0LAYs2iVNAiKCeVhFoy9ulrN8OsLGuCklKBVixHiMsT/HcrpORMfPQHl 15J3bCKWmg6K/RFJsy6T9tKnvruzPg9dMuaDUUovUz+V/2fHaXKP30iTqfPhLGmzMlwY Blb80e4qsVVQsgXFG9nHBUZBWF3TQ+crPzawd9rCLg0vVDvCoclFXBXKkdI69ROgY5QL OcliN3ew1ne/8518KhuyZrcfqkhBX2gTh0l40stGR5vjJkk31H4MkFqb8wcC/csOnQWT QsU+RU8zSBpXgSVOt/nked9mhtOuC8fvQT+k5KWwS1YS4an2GbFApQpX4s8CwU3aB6HU cv6g== X-Gm-Message-State: AOAM533X89AYdLSp3M4CuTqr+Ik0FHkwekzkbtTTyiOBAd3XGgbIKw/7 cWEJ+QfhLcnMBZ01qyxhhh0= X-Google-Smtp-Source: ABdhPJx8h8egIxNgUHun6X3TFdRmXDCCYFT6uZdi56iV9PmeB2Jf/QjOwB9/jdkeaymHcHy+D/Po2A== X-Received: by 2002:a17:902:7004:: with SMTP id y4mr8030515plk.52.1598366856067; Tue, 25 Aug 2020 07:47:36 -0700 (PDT) Return-Path: Received: from skjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id q2sm13919028pgs.90.2020.08.25.07.47.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Aug 2020 07:47:35 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW34'20 Date: Tue, 25 Aug 2020 07:47:35 -0700 Message-ID: <0f1c01d67aee$abf4a370$03ddea50$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdZ67iClWyEoNl/ORFO/pJ7EKTgcPQ== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0F1D_01D67AB3.FF9C8230" Content-Language: en-us ------=_NextPart_000_0F1D_01D67AB3.FF9C8230 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.2 M3 Next Deadline: YP 3.2 M3 build date 2020/8/31 - FEATURE FREEZE Next Team Meetings: * Bug Triage meeting Thursday Aug. 27th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Sept. 1st at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Aug. 25th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * YP 3.0.4 was released * M3 is due to close at the end of the week and this is the feature freeze point for 3.2 * After much debugging, we've concluded the bitbake cooker/server launch process is terminally flawed, you can't fork a python process into two independent python processes and have the internal python state machinery work correctly. As such, we're going to have to make some major changes to the way the bitbake cooker/server startup happens. * On a positive note, those server changes have forced many of the memory resident bitbake bugs to the surface and the new code appears to fix them, bringing memres bitbake much closer to being usable, maybe even becoming a default in this release if testing goes well. * There is concern about invasive changes like this with regard to LTS/dunfell where these bitbake bugs are also present. Ultimately we will make a decision about backporting based upon patch stability and user feedback from the LTS users. * We may delay M3 slightly to enable the bitbake server changes to merge since these are important for release and work making/merging. * The number of autobuilder intermittent bugs has continued to rise unfortunately. 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 with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing. * One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan cements.2FBugs * There is a proposal on the bitbake list to remove globbing support from file:// urls. Usage of these urls currently breaks source file checksumming which users don't realize, it can't be fixed in a sane way so and the most common use cases has easy alternatives such as referencing a directory as a file:// url without globs so removing globbing support appears to be the best way forward. * We have switched to the 5.8 kernel by default, it's taken a while to get through all the different issues but we appear to be there now, thanks to Bruce for working through many of them! * Some long standing musl SDK issues should be resolved now. YP 3.2 Milestone Dates: * 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.4 was released * YP 3.1.3 build date 2020/9/14 * YP 3.1.3 release date 2020/9/25 Tracking Metrics: * WDD 2424 (last week 2429) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1273 (last week 1271) * Patches in the Pending State: 502 (39%) [last week 495 (39%)] 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_0F1D_01D67AB3.FF9C8230 Content-Type: text/html; boundary="----=_NextPart_000_0ECA_01D66FB3.08937940"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.2 M3

Next Deadline: YP = 3.2 M3 build date 2020/8/31 - FEATURE FREEZE

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 3.0.4 was = released
  • M3 is due to close at the end = of the week and this is the feature freeze point for = 3.2
  • After much debugging, = we’ve concluded the bitbake cooker/server launch process is = terminally flawed, you can’t fork a python process into two = independent python processes and have the internal python state = machinery work correctly. As such, we’re going to have to make = some major changes to the way the bitbake cooker/server startup = happens.
  • On a positive note, those = server changes have forced many of the memory resident bitbake bugs to = the surface and the new code appears to fix them, bringing memres = bitbake much closer to being usable, maybe even becoming a default in = this release if testing goes well.
  • There is concern about invasive = changes like this with regard to LTS/dunfell where these bitbake bugs = are also present. Ultimately we will make a decision about backporting = based upon patch stability and user feedback from the LTS = users.
  • We may delay M3 slightly to = enable the bitbake server changes to merge since these are important for = release and work making/merging.
  • The number of autobuilder = intermittent bugs has continued to rise = unfortunately.

You can see the = list of failures we’re continuing to see by searching for the = “AB-INT” tag in bugzilla: https://bugzilla.y= octoproject.org/buglist.cgi?quicksearch=3DAB-INT

Help with any of = these would be much appreciated, unfortunately it is proving hard to = find anyone interested in helping figure these out and they = significantly hamper our testing.

  • One way to help the project is = to help us with bugs that are currently unassigned but ideally needed = during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Med= ium.2B_3.2_Unassigned_Enhancements.2FBugs
  • There is a proposal on the = bitbake list to remove globbing support from file:// urls. Usage of = these urls currently breaks source file checksumming which users = don’t realize, it can’t be fixed in a sane way so and the = most common use cases has easy alternatives such as referencing a = directory as a file:// url without globs so removing globbing support = appears to be the best way forward.
  • We have switched to the 5.8 = kernel by default, it's taken a while to get through all the different = issues but we appear to be there now, thanks to Bruce for working = through many of them!
  • Some long standing musl SDK = issues should be resolved now.

 

YP 3.2 Milestone = Dates:

  • 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.4 was = released
  • YP 3.1.3 build date = 2020/9/14
  • YP 3.1.3 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_0F1D_01D67AB3.FF9C8230--