From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-f176.google.com (mail-pl1-f176.google.com [209.85.214.176]) by mail.openembedded.org (Postfix) with ESMTP id EBB7C7F7C1 for ; Tue, 26 Nov 2019 15:47:13 +0000 (UTC) Received: by mail-pl1-f176.google.com with SMTP id w7so8295412plz.12 for ; Tue, 26 Nov 2019 07:47:15 -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=O291oCuDZhEivJKPoB7vR88Fu9O6n575GYkQLvGFs9s=; b=U4fglQ+E8Cpf47C+ClQqx1VE7amGeZsf+X2NOFqBoIsEmjxe38BLw0EC9xsgfrEFqp ZFykhCgqdzou4oC4zNvx2cdaUu1e2gCzIw/iX8wmCV9F6IsWATsFISlj2mUfV55/mFAq j3FKjJpqG0heR0IVsEfXA7yoXCQk5sn3ST+AY43RxhWiQxuIJ/L7dYC1i9onoCb2CnhJ 84JJsg6junuk8lMuC4YKT570v0OA0/193+dlLgwJsZ9nxTc6vxUrryBomZIUUZoDrE8V +so7TD4bdeVhHcUiaWfeYsx2iZC8pC6ioLyMQYyG8e0oHdxg3JkdpSXgaZfaC+h5P16t 8HPg== 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=O291oCuDZhEivJKPoB7vR88Fu9O6n575GYkQLvGFs9s=; b=CN2VoKGgtahyZQmzT0VIYdPnAX5OZ/uLTlRoosp/BrxKjKoV7/qouNyDQXeb3QvTRQ b8vLAoe4FgwYvyXqdMFDXrNcOMZjgtnI4DWRH2lKeov6CnC7j+FQwAyk3vHkEhzCz+z8 BrbuIiriBc0pbdKHZDhiPup2qYLUaYsEe9P5ph/rOa/g8Ri+6pv08XDlMO8ThbRAAWzY pKDBgQoIOdbAe7aR3dHWLX5Kkw4TLIooTv8hv5uzwpiqg9/pqHHeLjNIlTIQ+EOp1TFd xcSi9JKWDu7Y1SRMiIu45e0iMPNxBNC5k5/P3HXWbufR/hxjvjhUHxaexYvknLJbkCZm +pJg== X-Gm-Message-State: APjAAAW2aTtT0TC7VsSS1/AKYgmXiF/CobksdeLPxzFzyEca3ubgWdAB JMhHu3p70V7fAacqDHTOCo4= X-Google-Smtp-Source: APXvYqxq1xnhA8ILe5pPOp35LLRPhJ24K8tHfOaeT4Njjoq5oDGdDXiNGDpdQ7q0F+CM0m3l7o930Q== X-Received: by 2002:a17:902:a709:: with SMTP id w9mr35413431plq.235.1574783234732; Tue, 26 Nov 2019 07:47:14 -0800 (PST) Received: from sjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id y26sm13352876pfo.76.2019.11.26.07.47.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Nov 2019 07:47:14 -0800 (PST) From: To: , Date: Tue, 26 Nov 2019 07:47:14 -0800 Message-ID: <05d101d5a470$c69d7d00$53d87700$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdWkcLPLTDoMgQNQRQe65fqaczh1MQ== Subject: Yocto Project Status WW48'19 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, 26 Nov 2019 15:47:14 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_05D2_01D5A42D.B87BC3A0" Content-Language: en-us ------=_NextPart_000_05D2_01D5A42D.B87BC3A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M1 Next Deadline: YP 3.1 M1 build Dec. 2, 2019 Next Team Meetings: * Bug Triage meeting Thursday Dec. 5th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Dec. 3rd at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Nov. 26th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Dec. 10th at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * YP 2.7.2 should be released imminently. * The reproducibility issues from last week have been addressed and we are hoping to enable this by default soon, thanks to everyone who helped fix issues. * The news for hash equivalence is not so promising. Whilst a number of bugs were fixed, we've found a major problem which explains some of the failures we've seen and are currently working out how we may be able to resolve that issue. * Intermittent build failures continue to hamper builds, particularly combined with the above issues and as few people are available to attempt to debug and resolve them. * The focus on hash equivalence and reproducibility has slowed patch merging in other areas. Patch testing has been problematic as there are a lot of regressions being found in submitted patches which also slows down the whole merging process. * 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 next couple of 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 * Due to the number of key fixes being found we have delayed YP 3.0.1 being built slightly whilst we merge those fixes, it should build in the next few days. * If anyone has any status items for the project they'd like to add to the weekly reports, please email Richard and Stephen. Proposed YP 3.1 Milestone Dates: * YP 3.1 M1 Proposed build date 12/2/2019 * YP 3.1 M1 Proposed release date 12/13/2019 * YP 3.1 M2 Proposed build date 1/20/2020 * YP 3.1 M2 Proposed release date 1/31/2020 * YP 3.1 M3 Proposed build date 2/24/2020 * YP 3.1 M3 Proposed release date 3/6/2020 * YP 3.1 M4 Proposed build date 3/30/2020 * YP 3.1 M4 Proposed release date 4/24/2020 Planned upcoming dot releases: * YP 2.7.2 Should release this week. * YP 3.0.1 Proposed build date 11/25/2019 * YP 3.0.1 Proposed release date 12/06/2019 * YP 2.7.3 Proposed build date 2/10/20 * YP 2.7.3 Proposed release date 2/21/20 * YP 3.0.2 Proposed build date 2/3/20 * YP 3.0.2 Proposed release date 2/14/20 Tracking Metrics: * WDD 2578 (last week 2533) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1450 (last week 1461) * Patches in the Pending State: 579 (40%) [last week 579 (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_05D2_01D5A42D.B87BC3A0 Content-Type: text/html; boundary="----=_NextPart_000_0334_01D59EAD.B2BF7400"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M1 

Next Deadline: YP = 3.1 M1 build Dec. 2, 2019

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 2.7.2 should be released = imminently.
  • The reproducibility issues from = last week have been addressed and we are hoping to enable this by = default soon, thanks to everyone who helped fix = issues.
  • The news for hash equivalence = is not so promising. Whilst a number of bugs were fixed, we’ve = found a major problem which explains some of the failures we’ve = seen and are currently working out how we may be able to resolve that = issue.
  • Intermittent build failures = continue to hamper builds, particularly combined with the above issues = and as few people are available to attempt to debug and resolve = them.
  • The focus on hash equivalence = and reproducibility has slowed patch merging in other areas. Patch = testing has been problematic as there are a lot of regressions being = found in submitted patches which also slows down the whole merging = process.
  • 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 next couple of = 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
  • Due to the number of key fixes = being found we have delayed YP 3.0.1 being built slightly whilst we = merge those fixes, it should build in the next few = days.
  • If anyone has any status items = for the project they’d like to add to the weekly reports, please = email Richard and Stephen.

 

Proposed YP 3.1 = Milestone Dates:

  • YP 3.1 M1 Proposed build date = 12/2/2019
  • YP 3.1 M1 Proposed release date = 12/13/2019
  • YP 3.1 M2 Proposed build date = 1/20/2020
  • YP 3.1 M2 Proposed release date = 1/31/2020
  • YP 3.1 M3 Proposed build date = 2/24/2020
  • YP 3.1 M3 Proposed release date = 3/6/2020
  • YP 3.1 M4 Proposed build = date  3/30/2020
  • YP 3.1 M4 Proposed release = date  4/24/2020

 

Planned upcoming = dot releases:

  • YP 2.7.2 Should release this = week.
  • YP 3.0.1 Proposed build = date  11/25/2019
  • YP 3.0.1 Proposed release date = 12/06/2019
  • YP 2.7.3 Proposed build = date  2/10/20
  • YP 2.7.3 Proposed release date = 2/21/20
  • YP 3.0.2 Proposed build = date  2/3/20
  • YP 3.0.2 Proposed release date = 2/14/20

 

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_05D2_01D5A42D.B87BC3A0--