[OE-core] Yocto Project Status WW24
Jolley, Stephen K
stephen.k.jolley at intel.com
Fri Jun 10 15:21:01 UTC 2016
Current Dev Position: YP 2.2 M1
Next Deadline: YP 2.2 cut off: June 13, 2016 [3 days - Monday!]
SWAT team rotation: Jussi -> Maxim
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* We continue to see various python v3 issues however these are on the most part comparatively minor.
* The Centos 7 auobuilder issues look to have been caused by XFS, switching to ext4 seems to have resolved it.
* We're expecting some large patchsets for toaster bootstrap v2 -> v3 and changes to move OE-Core/Sato to gtk3+, am hoping to get these into M1.
* Richard is starting a discussion on multi-configuration builds on the openembedded-architecture list.
* YP 2.0.2 was released last week
* We're now working on 2.1.1 with trial builds in preparation for a release
* 2.2 M1 is due next week
Key YP 2.2 Dates:
* YP 2.2 M1 cut off would be: 6/13/16
* YP 2.2 M1 release would be: 6/24/16
* YP 2.2 M2 cut off would be: 7/18/16
* YP 2.2 M2 release would be: 7/29/16
* YP 2.2 M3 cut off would be: 8/29/16
* YP 2.2 M3 release would be: 9/9/16
* YP 2.2 M4 cut off would be: 10/3/16
* YP 2.2 M4 release would be: 10/28/16
Tracking Metrics:
WDD 2599 (last week 2622)
(https://wiki.yoctoproject.org/charts/combo.html)
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.2_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.2_Features
[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.jolley at intel.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160610/472a62f2/attachment-0002.html>
More information about the Openembedded-core
mailing list