From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-f65.google.com (mail-io1-f65.google.com [209.85.166.65]) by mail.openembedded.org (Postfix) with ESMTP id F05BB7F307 for ; Tue, 30 Jul 2019 15:15:40 +0000 (UTC) Received: by mail-io1-f65.google.com with SMTP id s7so128736428iob.11 for ; Tue, 30 Jul 2019 08:15:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version:thread-index :content-language; bh=Mk8dhrPnLzrZL0LZDknb2uE4iUTq0hjOk5Z+iCrXohk=; b=BVdz9hdGAwVfqDcNXpjvcoYKDBiXE+mTHqYVOoe4oEhM4f9zE1qLVIrki+f2ozAx1N NR43Xma8c9NZpvLl+EzWqxcfvTt+T5237EuGaSpz0QJKccjBWiAVuXyHk/J9H7W2wQ3e i8KfWuGTdTN3Ez2cKn2BMyVZOeLt5R8As8Y01TwJ5cSTar9PEOJ+/ZNhBGm+WFPolMwb cw7YK707CzpNJF7fSt0AOyEotJkr1j83qcNxW667VwW0agdCQihH/giAEbIV24M4t9W5 +JyovTL2qKiWZ5jr7vNDu0h89lUs/hXTWtoUX3lUF0AyjII/qlwtRUToZGKwkn32rIOh PP8g== 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:message-id:mime-version :thread-index:content-language; bh=Mk8dhrPnLzrZL0LZDknb2uE4iUTq0hjOk5Z+iCrXohk=; b=U1i8vMNPQ0oHYDXMoJRPwduHM5YJc7h+JbODX5XEJTADhf7mySDhLV8inh1rz6aJXZ dA9rKDUgL0xIZ3E/nquKgZwEVohlVgrnvEDCrY8T7/dFKES8bFoRGYWGBBAG1aLlApJo 5c805tXH/Q3jtUzeitjepewEMPAixiOnZLZnJNTJVUwpivs4H2bJ5wu7EehpfhSJPKe3 VbGQ18vbl5xzp+AmbaXT3+442rtIfCZqssexSHN8oIZ62wIj+9M56pSzEeNChJYWGw4a n+MamaSf1i8rqewimTV2tRGhzkZa+SzM8JHB/7PxFLKpkn/1USYtrnQeuyC8WRP+6R8Y d7nA== X-Gm-Message-State: APjAAAXXuWRi68ndi5DBOiS+3P1Ruw6wNb5Ox+zQq1feaeS1gFTImyfj fK+7AFy8AqRv/93lsCohHTo= X-Google-Smtp-Source: APXvYqx2gvcn45tzlj/EdmuVipuuvR/cO+DcCDemyPmr9GIEM5Ghmf5iFd6oUxKNp1VxtMPX1APYMg== X-Received: by 2002:a5e:d611:: with SMTP id w17mr40765827iom.63.1564499741915; Tue, 30 Jul 2019 08:15:41 -0700 (PDT) Received: from sjolley ([96.79.126.57]) by smtp.gmail.com with ESMTPSA id c17sm48653236ioo.82.2019.07.30.08.15.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jul 2019 08:15:41 -0700 (PDT) From: To: , Date: Tue, 30 Jul 2019 08:15:42 -0700 Message-ID: <04b301d546e9$a7e05980$f7a10c80$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdVG6U3wO4uG2Q0UTmaKawzyzLJwGw== Cc: Lieu.Ta@windriver.com Subject: Yocto Project Status WW31'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, 30 Jul 2019 15:15:41 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_04B4_01D546AE.FB83CB70" Content-Language: en-us ------=_NextPart_000_04B4_01D546AE.FB83CB70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 2.8 M3 Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019 SWAT Team Rotation: * SWAT lead is currently: Paul * SWAT team rotation: Paul -> Ross on Aug. 2, 2019 * SWAT team rotation: Ross -> Amanda on Aug. 9, 2019 * https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Next Team Meetings: * Bug Triage meeting Thursday August 1st at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday August 6th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday August 6th at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * YP 2.8 M2 rc1 is in QA which is due to complete on Wednesday * YP 2.6.3 will build to go into QA on Wednesday * We have a new "newcomer" bug category which are bugs suited to someone new to the project. These can be seen here: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs * The Yocto Project TSC has determined how it plans to operate and put the details into the appropriate wiki page: https://wiki.yoctoproject.org/wiki/TSC. It is intended as a decision making body of last resort, if there are issues people wish it to address, please raise them with one of its members. * After discussion in various places its been agreed that the next project release will be "3.0", to replace "2.8". The 2.8 placeholder may continue to be used, particularly in the bugzilla. There are many good reasons to bump the version, the most recent being the runqueue changes allowing build optimizations based upon output equivalence (see below) but also including the new project governance, the autobuilder, improved test coverage any many other things. * There are patches available which enable runqueue optimisations based on output comparisons of tasks. This removes the need to run later tasks if the output is unchanged and is based upon the previous hash equivalence server work. This feature should be a significant win for the users and is now working to a level where we'll likely make this a key feature of the next release. These patches are being tested in master-next at present. * There are also changes in -next which are being considered which change several bitbake APIs around runqueue. The feeling is now may be the best time to clean up several interfaces. If there are other API fixes people want to see, now is a good time to mention them. * The project is working on some mentor and mentee opportunities. Please see the separate email from Nicolas on the yocto list about this. Planned Releases for YP 2.8: * M2 is in QA * M2 Release 26th July * M3 Cutoff (Feature Freeze) 25th Aug * M3 Release 6th Sept * M4 Cutoff 30th Sept * 2.8 (M4) Final Release 25th Oct Planned upcoming dot releases: * YP 2.7.2 (Warrior) is planned for after 2.8 M2 release. * YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and before 2.8 M3. Tracking Metrics: * WDD 2466 (last week 2483) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1498 (last week 1499) * Patches in the Pending State: 619 (41%) [last week 623 (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 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_04B4_01D546AE.FB83CB70 Content-Type: text/html; boundary="----=_NextPart_000_006E_01D54144.3568CD60"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 2.8 M3

Next Deadline: YP = 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, = 2019

 

SWAT Team = Rotation:

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 2.8 M2 rc1 is in QA which is = due to complete on Wednesday
  • YP 2.6.3 will build to go into = QA on Wednesday
  • We have a new = “newcomer” bug category which are bugs suited to someone new = to the project. These can be seen here: https://wiki.yoctoproject.org/wiki/Bug_Triage#New= comer_Bugs
  • The Yocto Project TSC has = determined how it plans to operate and put the details into the = appropriate wiki page: https://wiki.yoctoproject.org/wiki/TSC= . It is intended as a decision making body of last resort, if there are = issues people wish it to address, please raise them with one of its = members.
  • After discussion in various = places its been agreed that the next project release will be = “3.0”, to replace “2.8”. The 2.8 placeholder may = continue to be used, particularly in the bugzilla. There are many good = reasons to bump the version, the most recent being the runqueue changes = allowing build optimizations based upon output equivalence (see below) = but also including the new project governance, the autobuilder, improved = test coverage any many other things.
  • There are patches available = which enable runqueue optimisations based on output comparisons of = tasks. This removes the need to run later tasks if the output is = unchanged and is based upon the previous hash equivalence server work. = This feature should be a significant win for the users and is now = working to a level where we’ll likely make this a key feature of = the next release. These patches are being tested in master-next at = present.
  • There are also changes in -next = which are being considered which change several bitbake APIs around = runqueue. The feeling is now may be the best time to clean up several = interfaces. If there are other API fixes people want to see, now is a = good time to mention them.
  • The project is working on some = mentor and mentee opportunities. Please see the separate email from = Nicolas on the yocto list about this.

 

Planned Releases = for YP 2.8:

  • M2 is in = QA
  • M2 Release 26th = July
  • M3 Cutoff (Feature Freeze) 25th = Aug
  • M3 Release 6th = Sept
  • M4 Cutoff 30th = Sept
  • 2.8 (M4) Final Release 25th = Oct

 

Planned upcoming = dot releases:

  • YP 2.7.2 (Warrior) is planned = for after 2.8 M2  release.
  • YP 2.6.3 (Thud) is intended for = build after 2.7.1 is complete and before 2.8 = M3.

 

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 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_04B4_01D546AE.FB83CB70--