From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-f176.google.com (mail-qt1-f176.google.com [209.85.160.176]) by mail.openembedded.org (Postfix) with ESMTP id 10B337F344 for ; Tue, 10 Sep 2019 15:00:09 +0000 (UTC) Received: by mail-qt1-f176.google.com with SMTP id r15so21052656qtn.12 for ; Tue, 10 Sep 2019 08:00:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:keywords:message-id:mime-version :content-language:thread-index; bh=oAytO9iCs6y2hkShJKYkddu9WKfb1jcxlEQgA1fiL5Q=; b=b73Wg9Hq+2G5h0dfSvIxc+45oPPLa2I8vQwELn5NEsOx+t63PnV9DCZjm3ct3zNr3V CVPnCAc/3JA71nax9CyVbezwxgWV6Bdze9ToDezczID11IdfwepWpkhuYPZpj9eOKnAT fnw1Dko404egmrCZ8GrYTgxE2FLL5vIhLfovRtQSqkqcvvqNY6lRNFi8dcWY+bw7+Xj4 ZTegoHoylH6N59k9mxynKBbn8En26uLWVbbupXVRthbJV34O5N3U/9IrXCqjQWzJmGxw qIXMgfsctOuH+/HJVGGiTcGnn8/FM+rh9vHKdOx5O+jmgna9aWOP/rUSv8jj9H6T1p9N IdFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:keywords:message-id :mime-version:content-language:thread-index; bh=oAytO9iCs6y2hkShJKYkddu9WKfb1jcxlEQgA1fiL5Q=; b=KXyymy05VOo5Ong6dRYE2z83KtU+udvWIdhFyR0/qq3ZTVtWM9kB+BoiKeCjhgJIK3 VMo3HiiYCGFvojonsFu4BdBw7UEZvyqvINzmstttBNULbvdYHgwPNOlQbQeD1yN3yEGT 5Pbpxqfk4sG3aWMZyMIX85CJArLShp3U8xrRYbVHl/3glYu2kCORSaaJTGN4TZmWob8I 7h3FmJpOh0wKx9XJT5/A/17BwB5loJJNTOwPBJG5ctFyZmrF8uWss37J+DvX65+4tgeo 5BrG2sW48Dylodzowtpa6XsUI13J4qf3wUXByyrR7OCCo1o5dAXjzHhn4Ua4MeXAEOt+ 0xRw== X-Gm-Message-State: APjAAAUGbZs9YKh02Lf3MoJmeQWm9PI38A4zkAx/aEGUklaD1c/ZEiPu XS2swmxCrkeA2MoUk4lbt+s= X-Google-Smtp-Source: APXvYqyYo1yItk5IKyfUNwi2lH4pMCBMuzZ7xg7BI7qvnBJQotHLX4JtDxEahjZSb+MKFt9/YmPODQ== X-Received: by 2002:ac8:74d5:: with SMTP id j21mr28963325qtr.60.1568127610777; Tue, 10 Sep 2019 08:00:10 -0700 (PDT) Received: from sjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id c185sm9294426qkf.122.2019.09.10.08.00.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Sep 2019 08:00:10 -0700 (PDT) From: To: , Date: Tue, 10 Sep 2019 08:00:08 -0700 Keywords: Yocto PM Work Message-ID: <073f01d567e8$70cf3900$526dab00$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdVn6EsK3mDUS8HzQc+7ATsiE7Gqkg== Cc: Lieu.Ta@windriver.com Subject: Yocto Project Status WW37'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, 10 Sep 2019 15:00:10 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0740_01D567AD.C472D200" Content-Language: en-us ------=_NextPart_000_0740_01D567AD.C472D200 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 2.8 M4 Feature Freeze Next Deadline: YP 3.0 Final Release 25th Oct SWAT Team Rotation: * SWAT lead is currently: Paul * SWAT team rotation: Paul -> Ross on Sept. 13, 2019 * SWAT team rotation: Ross -> Amanda on Sept. 20, 2019 * https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Next Team Meetings: * Bug Triage meeting Thursday Sept 12th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Oct. 1st at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Sept. 10th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Sept. 10th at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * We're now in feature freeze for 3.0 and working on bug fixing for final release * We have not built M3 yet as some work still remains for us to be feature complete and ready for QA. This puts us behind schedule but the plan is to complete the key features we've planned rather than adhere strictly to dates. We hope to make up time during M4 by having M3 at high quality and take advantage of our automation. * RP is away for the rest of the week which means M3 progress will be limited this week, Ross will queue patches. * Key 3.0 changes have now merged: * 5.2 linux-libc-kernel-headers * 5.2 kernel recipes by default for all reference BSPs * Removal of LSB and poky-lsb and replacement with alt config testing * systemd by default for poky-altcfg * Patches have significantly reduced the dependency on python2 * Reproducible builds are now being tested for core-image-minimal * Automated toolchain testsuite tests (binutils, gcc, glibc) * Key blocking issues for M3 that have been fixed: * Systemtap issues with 5.2 were debugged and patches sent/merged upstream * 5.2 dmesg on qemuarm64 fixed * qemumips hang when using highmem root caused and worked around (for now) * mdadm ptest timeout worked around * quilt and libevent ptest regressions from M2 resolved * Remaining issues blocking M3: * systemd boot failure on qemumips * strace ptest timeout * Hash equivalence performance problems (RP has a simple idea to ~double speed) * Hash equivalence bugs * Toolchain testsuite relocation bugs (Nathan working on it) * Hash Equivalency status: * Ideas about removing some dependency information from the hashes to allow faster bulk queries aren't viable so the current codebase approach is correct * we need to rework the client/server communication to scale to the autobuilder * there are some bugs in the code the autobuilder continues to expose * we have cases where its not 100% clear what the correct behaviour should be * test cases are proving to be problematic to write in a maintainable way * Documentation - Due to illness Scott is unavailable for the next month or two so doc patches will be handled by Richard or Ross in the short term. We'll likely limit them to correctness issues and defer any substantial new text. If anyone has availability and skills to work on the manuals please talk to us. We're aware there is a patch backlog. * If anyone has any status items for the project they'd like to add to the weekly reports, please email Richard+Stephen. Planned Releases for YP 3.0 {2.8}: * M3 Release 6th Sept * M4 Cutoff 30th Sept - this will be YP 3.0. * YP 3.0 {2.8 (M4)} Final Release 25th Oct Planned upcoming dot releases: * YP 2.7.2 (Warrior) is planned for after YP 3.0 release. * YP 2.6.4 (Thud) is planned for after YP 2.7.2 release. Tracking Metrics: * WDD 2424 (last week 2413) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1417 (last week 1470) * Patches in the Pending State: 582 (41%) [last week 611 (42%)] Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features 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_0740_01D567AD.C472D200 Content-Type: text/html; boundary="----=_NextPart_000_0115_01D551AC.08CBDAE0"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 2.8 M4 Feature Freeze

Next Deadline: YP = 3.0 Final Release 25th Oct

 

SWAT Team = Rotation:

 

Next Team = Meetings:

 

Key = Status/Updates:

  • We’re now in feature = freeze for 3.0 and working on bug fixing for final = release
  • We have not built M3 yet as = some work still remains for us to be feature complete and ready for QA. = This puts us behind schedule but the plan is to complete the key = features we’ve planned rather than adhere strictly to dates. We = hope to make up time during M4 by having M3 at high quality and take = advantage of our automation.
  • RP is away for the rest of the = week which means M3 progress will be limited this week, Ross will queue = patches.
  • Key 3.0 changes have now = merged:
    • 5.2 = linux-libc-kernel-headers
    • 5.2 kernel recipes by default = for all reference BSPs
    • Removal of LSB and poky-lsb and = replacement with alt config testing
    • systemd by default for = poky-altcfg
    • Patches have significantly = reduced the dependency on python2
    • Reproducible builds are now = being tested for core-image-minimal
    • Automated toolchain testsuite = tests (binutils, gcc, glibc)
  • Key blocking issues for M3 that = have been fixed:
    • Systemtap issues with 5.2 were = debugged and patches sent/merged upstream
    • 5.2 dmesg on qemuarm64 = fixed
    • qemumips hang when using = highmem root caused and worked around (for = now)
    • mdadm ptest timeout worked = around
    • quilt and libevent ptest = regressions from M2 resolved
  • Remaining issues blocking = M3:
    • systemd boot failure on = qemumips
    • strace ptest = timeout
    • Hash equivalence performance = problems (RP has a simple idea to ~double = speed)
    • Hash equivalence = bugs
    • Toolchain testsuite relocation = bugs (Nathan working on it)
  • Hash Equivalency = status:
    • Ideas about removing some = dependency information from the hashes to allow faster bulk queries = aren’t viable so the current codebase approach is = correct
    • we need to rework the = client/server communication to scale to the = autobuilder
    • there are some bugs in the code = the autobuilder continues to expose
    • we have cases where its not = 100% clear what the correct behaviour should = be
    • test cases are proving to be = problematic to write in a maintainable = way
  • Documentation - Due to illness = Scott is unavailable for the next month or two so doc patches will be = handled by Richard or Ross in the short term. We’ll likely limit = them to correctness issues and defer any substantial new text. If anyone = has availability and skills to work on the manuals please talk to us. = We’re aware there is a patch backlog.
  • If anyone has any status items = for the project they’d like to add to the weekly reports, please = email Richard+Stephen.

 

Planned Releases = for YP 3.0 {2.8}:

  • M3 Release 6th = Sept
  • M4 Cutoff 30th Sept - this will = be YP 3.0.
  • YP 3.0 {2.8 (M4)} Final Release = 25th Oct

 

Planned upcoming = dot releases:

  • YP 2.7.2 (Warrior) is planned = for after YP 3.0 release.
  • YP 2.6.4 (Thud) is planned for = after YP 2.7.2  release.

 

Tracking = Metrics:

 

Key Status Links = for YP:

https://wiki.yoctoproject.or= g/wiki/Yocto_Project_v2.8_Status

https://wiki.yoctoproject.or= g/wiki/Yocto_2.8_Schedule

https://wiki.yoctoproject.or= g/wiki/Yocto_2.8_Features

 

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_0740_01D567AD.C472D200--