Current Dev Position: YP 2.1 Planning
Next Deadline: YP 2.1 M1 Cutoff December 7, 2015 noon GMT

SWAT team rotation: Tracy -> Alejandro
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Key Status/Updates:

  *   2.0 was released!
  *   Undergoing planning for 2.1
  *   Have various queued patches being processed ready for merging
  *   Found a key performance improvement in bitbake cache handling which will 
improve bitbake interactivity (bitbake -p with hot cache is about twice as fast)
  *   Initial focus on 2.1 is like dealing with autobuilder issues remaining 
from 2.0 and looking at tooling/process improvements to patch workflow, SWAT 
team and error reporting/handling

Key YP 2.1 Dates:
YP 2.1 M1 Cutoff (Feature Freeze) date is December 7, 2015 noon GMT
YP 2.1 M1 Target release date is December 24, 2015
YP 2.1 M2 Cutoff (Feature Freeze) date is January 25, 2016 noon GMT
YP 2.1 M2 Target release date is February 12, 2016
YP 2.1 M3 Cutoff (Feature Freeze) date is February 29, 2016 noon GMT
YP 2.1 M3 Target release date is March 18, 2016
YP 2.1 M4 / Final Cutoff: March 28, 2016 noon GMT - Stabilization only 
milestone.
YP 2.1 Final Release Target: April 29, 2016

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.1_Features

Tracking Metrics:
            WDD 2181 (last week 2089)
(https://wiki.yoctoproject.org/charts/combo.html)

[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
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:          (503) 712-0534
*    Cell:                                (208) 244-4460
* Email:                             stephen.k.jol...@intel.com

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

Reply via email to