Current Dev Position: YP 2.5 is in QA.

Next Deadline: YP 2.5 M4 release is 4/27/18


SWAT Team Rotation:

SWAT lead is currently: Stephano

SWAT team rotation: Stephano -> Stephano on May 4, 2018

SWAT team rotation: Stephano -> Maxin on May 11, 2018

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:

  *   2.5 rc1 is in QA
  *   As things stand we are aware of some minor issues in rc1 such as the 
bitbake version not having been updated and a fix for the eclipse plugin being 
missing. A workaround is available for the latter. We will let QA run its 
course before deciding on whether an rc2 makes sense.
  *   The monthly technical call is tomorrow (1st May) and will focus on 2.6 
planning discussion (https://www.yoctoproject.org/monthly-technical-call/). The 
email linked to below details the planning process we will be following along 
with some of the possible ideas for 2.6: 
http://lists.openembedded.org/pipermail/openembedded-core/2018-April/150040.html


Planned upcoming dot releases:

YP 2.3.4 (Pyro) will be built after 2.5

YP 2.2.4 (Morty) will be built after 2.5

YP 2.4.3 (Rocko) is planned for post YP 2.5


Key YP 2.5 Dates are:

YP 2.5 M4 release of 4/27/18


Tracking Metrics:

  *   WDD 2508 (last week 2486) 
(https://wiki.yoctoproject.org/charts/combo.html)
  *   Patches
     *   Same as last week as nothing has merged.
     *   Total patches found: 1635
     *   Percentage of patches in the Pending State: 46%


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.5_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!]

-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to