From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f176.google.com (mail-pg1-f176.google.com [209.85.215.176]) by mail.openembedded.org (Postfix) with ESMTP id 0A5497FDAC for ; Tue, 7 Jan 2020 15:59:47 +0000 (UTC) Received: by mail-pg1-f176.google.com with SMTP id k3so93102pgc.3 for ; Tue, 07 Jan 2020 07:59:49 -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:thread-index :content-language; bh=izgGRGrehLEMIjcyjOQBvTForeL0VZEv5bw5Drne05o=; b=HE/8SBMGSA/P3xOujrKD/gXcpbMVe9qvSHszcc1wlX6H+WYK+VnUw6DtqMxEb0eurr LrPx6KlfeLVUli/IoTeJGbFneh1WZjOLnwCE+fRp87xdRPpeXzmGoibW+ya4BA1o1b3Y hvvZJjuW/4oG12IzrakstxmXQz1Jm/oVs0N4v/Hcskg2j+DD9mEOPAEtfEAZg63LrHQ+ Xrg/1dguPMHaEZgLL2z503euvm1oNwxXvdOlAf57HMSmNy0VVZ3Iyl77mqNhA+KKICpO zWklwoAe9cB44srgJHiUh6F77B+FWQB11MYDnn4+oSian/aHQavNgDNyljfM1zQLE2c6 nUbg== 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=izgGRGrehLEMIjcyjOQBvTForeL0VZEv5bw5Drne05o=; b=r6H3WIZh9Zvo/+K9Seus81hpIRk/QTVcOdKB+u7ACgDme4by7bmYWux0JCbV4QIOkU 7mW/URLbpWaDJQNLFKy5cSd7Tr82MewEspeO4ztbsuQfqXvD+zvk+wQAGl1LSy5iSQit 9SnC7XDuGCt1mSom2q6Q8gnxLnpmZPk+XDlkXyxi77g7nYA19Cs3aOPeIWDcY9bub+Uz ekt1K3UKjfnp6+ElTwqe5cqAyE9XYV2+TaFvUz29JXuiOslWCA43VSnqkQizQdwuPqh+ pIzocqXY8sKgY+vcjjgin+WZgPo+aOHWf9MQXcYardGt8HY5dHR68+08IyLiaq/MHmgb mBYA== X-Gm-Message-State: APjAAAU9xMiyLUsbYaqIojcCFe3jL6pa0q4yz+iMUK2r9ceZLOviPeeD HcrMXktJRJG4KKeOsqkVc8U= X-Google-Smtp-Source: APXvYqzUqO/SF0N2frigO5TAZHne6obagnNYfFBB7HHwePf63LFmrEyfnZE4JvfI0Q6flF4uHavlYw== X-Received: by 2002:a63:4465:: with SMTP id t37mr118316pgk.256.1578412788904; Tue, 07 Jan 2020 07:59:48 -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 b98sm29351806pjc.16.2020.01.07.07.59.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Jan 2020 07:59:48 -0800 (PST) From: To: , Date: Tue, 7 Jan 2020 07:59:48 -0800 Message-ID: <184e01d5c573$7d81b0e0$788512a0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdXFc0pz+rFWOT8aReCBYYWyKgeNkQ== Subject: Yocto Project Status WW02'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, 07 Jan 2020 15:59:48 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_184F_01D5C530.6F606CB0" Content-Language: en-us ------=_NextPart_000_184F_01D5C530.6F606CB0 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. 9th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Jan. 7th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Jan. 14th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Jan. 14th at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * YP 3.1 M1 was released. * Over the last two weeks there were a number of significant fixes for hash equivalence which should resolve some of the long standing bugs reported here. Some of these fixes may require further architectural tweaks to the codebase but those are cleanups which can happen in due course now the root causes are identified. * There are performance issues that remain in hash equivalence but these will be looked at only once the correctness issues and intermittent test failures are addressed. * There are some puzzling selftest failures that remain, in particular a locked signatures one which seems to be caused through bad interaction with the hash equivalence code but is intermittent and does not make sense. * The patch queue for master should be roughly up to date which some key changes such as the gettext upgrade having merged recently. Some pending changes like the glibc upgrade look problematic. * A key functionality change has merged this week where the layout of the sstate directory has changed. This was done to try and improve performance and handle some performance issues where the previous code simply wasn't scaling. There is no user visible impact but it does mean new sstate will be generated into a new layout and the older sstate will be ignored. The sstate filename length issues should also be addressed by this patchset. * Whilst the SWAT process is disbanded, the effect of this is that Richard now has to file the bugs personally. This distracts from other things that could be worked on. * 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. * The TSC is working on LTS plans, productive discussions have been had and a new policy on handling this and stable releases should be available in the coming weeks. * We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjn ABc/edit?usp=sharing 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 2773 (last week 2783) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1400 (last week 1400) * Patches in the Pending State: 562 (40%) [last week 561 (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 Project Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_184F_01D5C530.6F606CB0 Content-Type: text/html; boundary="----=_NextPart_000_1777E_01D5B4B1.09C8BFE0"; 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:

 

Key = Status/Updates:

  • YP 3.1 M1 was = released.
  • Over the last two weeks there = were a number of significant fixes for hash equivalence which should = resolve some of the long standing bugs reported here. Some of these = fixes may require further architectural tweaks to the codebase but those = are cleanups which can happen in due course now the root causes are = identified.
  • There are performance issues = that remain in hash equivalence but these will be looked at only once = the correctness issues and intermittent test failures are = addressed.
  • There are some puzzling = selftest failures that remain, in particular a locked signatures one = which seems to be caused through bad interaction with the hash = equivalence code but is intermittent and does not make = sense.
  • The patch queue for master = should be roughly up to date which some key changes such as the gettext = upgrade having merged recently. Some pending changes like the glibc = upgrade look problematic.
  • A key functionality change has = merged this week where the layout of the sstate directory has changed. = This was done to try and improve performance and handle some performance = issues where the previous code simply wasn’t scaling. There is no = user visible impact but it does mean new sstate will be generated into a = new layout and the older sstate will be ignored. The sstate filename = length issues should also be addressed by this = patchset.
  • Whilst the SWAT process is = disbanded, the effect of this is that Richard now has to file the bugs = personally. This distracts from other things that could be worked = on.
  • 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.
  • The TSC is working on LTS = plans, productive discussions have been had and a new policy on handling = this and stable releases should be available in the coming = weeks.
  • We are continuing to collect = ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-= pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=3Dsharing

 

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 Project Manager

(    Cell:         = ;       (208) = 244-4460

* Email:           = ;   sjolley.yp.pm@gmail.com

 

------=_NextPart_000_184F_01D5C530.6F606CB0--