From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f51.google.com (mail-pj1-f51.google.com [209.85.216.51]) by mx.groups.io with SMTP id smtpd.web10.29478.1599595525552681818 for ; Tue, 08 Sep 2020 13:05:25 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=kbrZErTP; spf=pass (domain: gmail.com, ip: 209.85.216.51, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pj1-f51.google.com with SMTP id b16so165225pjp.0 for ; Tue, 08 Sep 2020 13:05:25 -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=M80U+oLwdOMXhrY3fgyqk1qwS/UFoOOxdAfepLMpTjs=; b=kbrZErTP6QdTHI4xnP9bQrJjezmSIqjTcHJDGUcE9KlEQi8Am4l/gq+SIk5UkopQ6I KKbiFyhAUoQZoNLvUsgipwgSX7ncj+6eQXjIPhqAeLUdnNwXL5MzZ3/+WHTZZv4WLspG peKQxqIueHIjMxMuPNWa6zoPwYeiIib+tuNF6UPr9Kju9GOZLRlDiZFZgKLQTV9XL4lI F6Ug2Hq8DRd8ocbtcCfyZ12Uv/6QIICz27kOkCeJ0s2+Ik2250KvRD1brISpFkwo9B5E Ng9FfQvN7CDEiCjRBlPFscWhp2CqEi2/gbLXQyvBwI5v8bQl2x0YO8oTB/Cz/SkZ5JE+ nyBw== 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=M80U+oLwdOMXhrY3fgyqk1qwS/UFoOOxdAfepLMpTjs=; b=J3rx75gYhoItsT9abxT+AYABW8l5CaFX6u9fehsikgMI6rU+AwEfEtfA2DxQi+Uapk zf0I7v4MuK4KUcR32J22rlHxo0Ox2m0X5lc8Mvw4LNSrijw9secT5wsuc3pu4r0kM7rm v/4vTf+hAn8LrIsCR51WZPbsgcDhKYLv2X6qvfOVTOuzMs81+7GYJCLU0VaSVkbXn8Sl 5nNp12N4gBq/jiK/T1nSIiiQ2KIuGyJfotqfm+UyG4i0p4uV3pA0BHluSdQu3NYbMo7Y spTEjH98SJ88tNNlMbw2dE5aNlZRFcuh3x62Vh4BwpUssrUgVprCF03y8xKdUibcKD2c kuRQ== X-Gm-Message-State: AOAM530hJUM5L3RNj0eHEviGPvuc/AWybayYVMJSrPV2ANi8J+NSoHAg 0E0IXRpvDFt/MAq6Z1gR4jc= X-Google-Smtp-Source: ABdhPJy1DWlF7reeaoET9Q+qXYdqjV4WEHJ2Wwu3iW0MWdBmZFMkQI86tQW3r/Loo62FVl7fVdOtnQ== X-Received: by 2002:a17:90a:d793:: with SMTP id z19mr439678pju.12.1599595523574; Tue, 08 Sep 2020 13:05:23 -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 k28sm231533pfh.196.2020.09.08.13.05.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Sep 2020 13:05:23 -0700 (PDT) From: "Stephen Jolley" To: , Subject: Yocto Project Status WW36'20 Date: Tue, 8 Sep 2020 13:05:23 -0700 Message-ID: <006701d6861b$634566e0$29d034a0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdaF7Aj9k3vOLG1QQD25eKQyInsZ0Q== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0068_01D685E0.B6EB70E0" Content-Language: en-us ------=_NextPart_000_0068_01D685E0.B6EB70E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.2 M3 Next Deadline: YP 3.2 M3 Feature Freeze - Now Next Team Meetings: * Bug Triage meeting Thursday Sept. 10th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Oct. 6th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Sept. 8th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * M3 has now closed and we're at feature freeze for 3.2. * We now have most patches merged for 3.2, the main remaining question is around the documentation. The current plan is to merge the sphinx branches into master and then build M3. * There is a new technique being used to try and mitigate some of the runtime autobuilder issues, so far the results from that have looked promising (using the runqemu-renice script). * Some fixes for bitbake's parsing handling have merged which hopefully will address some of the hung process issues we've been seeing. Some of the issues look like potential issues in upstream python multiprocessing. * There have also been significant cleanups to the server process logging and reporting of processes holding the bitbake lock. * The work in enabling PRServ to work well with hash equivalence has merged. * A preview of the sphinx built documentation is now available at https://docs.yoctoproject.org/, work is ongoing to complete the migration work. * We continue to struggle with a number of autobuilder intermittent bugs. 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 * For older releases, we've been struggling to handle these with the changing distros on the autobuilder infrastructure. We've managed to pull together various pieces of work to allow these older releases to be built on the infrastructure and an email discussing this was sent to the openembedded-architecture list. It will mean adding some larger series of patches to the older release branches for the yocto-autobuilder-helper and openembedded-core repositories but it is believed this is in the best interests of being able to test these older releases going forward if needed. This may also reduce the barrier to entry for new maintainers and community maintenance. 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.1.3 build date 2020/9/14 * YP 3.1.3 release date 2020/9/25 Tracking Metrics: * WDD 2461 (last week 2436) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1264 (last week 1264) * Patches in the Pending State: 502 (40%) [last week 502 (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_0068_01D685E0.B6EB70E0 Content-Type: text/html; boundary="----=_NextPart_000_0F1D_01D67AB3.FF9C8230"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.2 M3

Next Deadline: YP = 3.2 M3 Feature Freeze - Now

 

Next Team = Meetings:

 

Key = Status/Updates:

  • M3 has now closed and = we’re at feature freeze for 3.2.
  • We now have most patches merged = for 3.2, the main remaining question is around the documentation. The = current plan is to merge the sphinx branches into master and then build = M3.
  • There is a new technique being = used to try and mitigate some of the runtime autobuilder issues, so far = the results from that have looked promising (using the runqemu-renice = script).
  • Some fixes for bitbake’s = parsing handling have merged which hopefully will address some of the = hung process issues we’ve been seeing. Some of the issues look = like potential issues in upstream python = multiprocessing.
  • There have also been = significant cleanups to the server process logging and reporting of = processes holding the bitbake lock.
  • The work in enabling PRServ to = work well with hash equivalence has merged.
  • A preview of the sphinx built = documentation is now available at https://docs.yoctoproject.org/, work = is ongoing to complete the migration work.
  • We continue to struggle with a = number of autobuilder intermittent bugs. 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?qui= cksearch=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
  • For older releases, we’ve = been struggling to handle these with the changing distros on the = autobuilder infrastructure. We’ve managed to pull together various = pieces of work to allow these older releases to be built on the = infrastructure and an email discussing this was sent to the = openembedded-architecture list. It will mean adding some larger series = of patches to the older release branches for the = yocto-autobuilder-helper and openembedded-core repositories but it is = believed this is in the best interests of being able to test these older = releases going forward if needed. This may also reduce the barrier to = entry for new maintainers and community = maintenance.

 

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.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_0068_01D685E0.B6EB70E0--