Re: Yocto Project Status WW09

[Philip Balister <philip@balister.org>]

On 02/26/2016 12:36 PM, Richard Purdie wrote:
> Current Dev Position: YP 2.1 M3
> Next Deadline: YP 2.1 M3 Cutoff (Feature Freeze) February 29, 2016
>  
> SWAT team rotation: Tracy -> Alejandero
> https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>  
> Key Status/Updates:
> * 2.1 Feature Freeze is upon us. If there is any feature you want to 
>   see in 2.1 which isn't going to make the deadline, talk to RP.
> * We plan to release 2.1 M2 despite the sato glib issue, granting an
>   exception for the high bug and then  concentrate on 2.1 M3.
> * 2.1 M3 build won't happen until sato glib issue resolved.
> * Also planning to merge the gobject-introspection changes 
> * Pseudo connection issue appears to be addressed with increased retry 
>   numbers. Tests ongoing.
> * We're about to try and transition meta-yocto within meta-yocto to 
>   meta-poky. The amount of pain this is causing is horrible :(.

Thanks for doing this. Can you summarize the pain? Are there any
important lessons here?

Philip

> * We're considering a bump in the minimum git version requirements 
>   due to the requirements of various pieces of project tooling.
> * We're rebuilding jethro 2.0.1 due to the glibc security issue, now 
>   at -rc7.
>  
> Key YP 2.1 Dates:
> YP 2.1 M2 Target release date is February 12, 2016 (Will slip a few
> weeks.)
> 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 2565 (last week 2585)
> (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,
>  
> Richard
> 
> 
> 
> 
>