From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-f41.google.com (mail-pj1-f41.google.com [209.85.216.41]) by mail.openembedded.org (Postfix) with ESMTP id F41937FD54 for ; Tue, 21 Jan 2020 15:49:57 +0000 (UTC) Received: by mail-pj1-f41.google.com with SMTP id m13so1737928pjb.2 for ; Tue, 21 Jan 2020 07:49:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version:content-language :thread-index; bh=hT6iVoerQQy0dgCIpTpGoqqpHtryPBvxTZz3Pkwm+uw=; b=qsoyCXETVRX1/HrAwqDnlZhueD0C/I3NEFc0sN/V/h6E1Ds5akTi762CNhwrn5freZ QhUkJ3tUF4d6G6MoJUuCz9iFirn5oUBwaO37giOM4Ag1HaXrQwjy1QKPiNLJnQ+Nfejs 80FGPMii1gSSBQSbFmiyMnaw+zfgVuJrzv+HSg/ubG1XpLc4LRdOSerMUHEwFZym7Sar WW2XCiNF/qEtLMuvtkk020SOi6jkP+uGsJtzcD2gHA0EfoochlBjCQmPsPEokcZY9tbO oUlbLdfQiQ7cPovtG29wlsqO/uKPn1xyIm3pn5ld6lUR8kaulz2KmtuVkfBASyEZlDFs dQLw== 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 :content-language:thread-index; bh=hT6iVoerQQy0dgCIpTpGoqqpHtryPBvxTZz3Pkwm+uw=; b=bEF3U9DwoWKd383U4wMZSi9A47oA/wFAnNHqTMFwUK1KCbvWh8n1CAtMu0YbkDaRw0 up0Xo1aK86KzH/hZkJ4xZ2aehFuEbu96Y05Wkjg9Q1niqGGR4TqawYTHjFleuwjEP5GL l1UTSX6Q4BTTfO6c7X8mWCr1l1GRUf/hTSn3PM0BvN6c0xcTpUdLBlyBBdZRnSD1Bo9R RKAPnni3J/CvCkJ/E516qXz60YklyqQxa04b0CWzb6XbAKKwCZZ+6qgtFojWxcMnioFx VZAY6W27jPClNKkRB5CGQUtne+DbYCEoFGUZbrQAxCQOTXYKxa1+lz2+ANta5my0y7ty 7M5g== X-Gm-Message-State: APjAAAUDdi3yy/QoLOc2mz2zsXxVYmzPzq3LOpkEmR7WK3UVcw16/ArG 9vjgJ6UF5LTmn1HfSRZ+/ow= X-Google-Smtp-Source: APXvYqxaxg+BiyGBEUN7Rb7Lkh5KBA8GYuivympL1tfyPunFNhcR5FK7sp+vJmFWwt0/M05kTlr5wA== X-Received: by 2002:a17:902:ba91:: with SMTP id k17mr5810955pls.228.1579621798976; Tue, 21 Jan 2020 07:49:58 -0800 (PST) Received: from skjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id z6sm43972785pfa.155.2020.01.21.07.49.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Jan 2020 07:49:58 -0800 (PST) From: To: , Date: Tue, 21 Jan 2020 07:49:58 -0800 Message-ID: <0c3801d5d072$6f4f1300$4ded3900$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdXQb5briFxg5tEuSSKCi1BOi+KBrQ== Subject: Yocto Project Status WW04'20 X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2020 15:49:58 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0C39_01D5D02F.61303FD0" Content-Language: en-us ------=_NextPart_000_0C39_01D5D02F.61303FD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M2 Next Deadline: YP 3.1 M2 build date 1/20/2020 Next Team Meetings: * Bug Triage meeting Thursday Jan. 23th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Feb. 4th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Jan. 21th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Feb. 11th at 8am PDT ( https://www.twitch.tv/yocto_project) Tip of the Week: * 'You can quickly test a change to a recipe on a target by rebuilding it alone, then rsyncing pieces of WORKDIR/image/ or WORKDIR/packages-split/PACKAGENAME/ rather than rebuilding the image (bit of a hack but effective). * (anyone with tips they'd like to see here, please send to Stephen or Richard) Key Status/Updates: * YP 3.1 M2 will build shortly, the only remaining blocking issue is the buildtools-extended-tarball fixes which should happen today. * Python 2 has been finally removed from OE-Core. This was long scheduled and whilst its causing problems for other layers, we really need to resolve those issues now rather than later in the release cycle so it is the right time to finally do this. * Patch merging continues to be making good progress and staying roughly up to date. * The patch metrics showed significant improvement this week, partly from continuing work done by Alex Kanavin in keeping things up to date but also from the python2 removal. * Bruce is struggling to get the 5.4 kernel to work on all platforms and any help, particularly with MIPS would be much appreciated. This is blocking the kernel updates at this point. * We're starting to see problems as distros enable seccomp in file which then conflicts with our use of pseudo. We need to come up with a better fix but for now, a wrapper script which adds "-S" to the command line for file, injected into PATH is a workaround. * There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage. * There is a separate email about buildtools tarballs continuing toolchains to support building on wider combinations of host distros, please see that for more info if interested in this. * We continue to struggle to get clean 'full' builds. * The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated. YP 3.1 Milestone Dates: * YP 3.1 M2 build date 1/20/2020 * YP 3.1 M2 release date 1/31/2020 * 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 2.7.3 build date 2/10/2020 * YP 2.7.3 release date 2/21/2020 * YP 3.0.2 build date 2/3/2020 * YP 3.0.2 release date 2/14/2020 Tracking Metrics: * WDD 2758 (last week 2772) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1357 (last week 1411) * Patches in the Pending State: 536 (39%) [last week 562 (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_0C39_01D5D02F.61303FD0 Content-Type: text/html; boundary="----=_NextPart_000_0749_01D5CAAF.933EED80"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M2

Next Deadline: YP = 3.1 M2 build date 1/20/2020

 

Next Team = Meetings:

 

Tip of the = Week:

  • ‘You can quickly test a = change to a recipe on a target by rebuilding it alone, then rsyncing = pieces of WORKDIR/image/ or WORKDIR/packages-split/PACKAGENAME/ rather = than rebuilding the image (bit of a hack but = effective).
  • (anyone with tips they’d = like to see here, please send to Stephen or = Richard)

 

Key = Status/Updates:

  • YP 3.1 M2 will build shortly, = the only remaining blocking issue is the buildtools-extended-tarball = fixes which should happen today.
  • Python 2 has been finally = removed from OE-Core. This was long scheduled and whilst its causing = problems for other layers, we really need to resolve those issues now = rather than later in the release cycle so it is the right time to = finally do this.
  • Patch merging continues to be = making good progress and staying roughly up to = date.
  • The patch metrics showed = significant improvement this week, partly from continuing work done by = Alex Kanavin in keeping things up to date but also from the python2 = removal.
  • Bruce is struggling to get the = 5.4 kernel to work on all platforms and any help, particularly with MIPS = would be much appreciated. This is blocking the kernel updates at this = point.
  • We’re starting to see = problems as distros enable seccomp in file which then conflicts with our = use of pseudo. We need to come up with a better fix but for now, a = wrapper script which adds “-S” to the command line for file, = injected into PATH is a workaround.
  • There is continued concern = about the number of recurring/intermittent failures in the automated = testing, mostly from selftest and testimage.
  • There is a separate email about = buildtools tarballs continuing toolchains to support building on wider = combinations of host distros, please see that for more info if = interested in this.
  • We continue to struggle to get = clean ‘full’ builds.
  • The triage team is worried = about attendance at triage meetings and the project is finding it hard = to find people to help fix bugs. If anyone is willing to work on bugs, = assistance would be greatly appreciated.

 

YP 3.1 Milestone = Dates:

  • YP 3.1 M2 build date = 1/20/2020
  • YP 3.1 M2 release date = 1/31/2020
  • 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 2.7.3 build date  = 2/10/2020
  • YP 2.7.3 release date = 2/21/2020
  • YP 3.0.2 build date  = 2/3/2020
  • YP 3.0.2 release date = 2/14/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_0C39_01D5D02F.61303FD0--