All, We have built out and tested the 1.5 milestone 2 release and after quite a bit of discussion have decided not to release it. I want to spend a few moments to explain what happened with M2 and why this is actually a good thing.
One of the things that we wanted to do early in the 1.5 time period is upgrade the toolchain. Whenever you do a major upgrade of something that just about everything requires, you end up exposing a lot issues. In the case of M2 this caused quite a number of issues, most of which have been already sorted out in master. (see https://wiki.yoctoproject.org/wiki/WW27_-_2013-07-03-3_-_Fullpass_Yocto_1.5_M2.RC1 for the full details). Specifically, this upgrade caused two very major issues: - Two of the four core BSPs failed to boot. This was a combination of an updated gcc not playing nice with an updated kernel. This has been fixed. - udev-cache failed for all poky-lsb images (and the build appliance). This was fixed at: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=f1f5f7d3b45adb4e6d52dec11462fa658ccda1ec With the average Yocto Project release build containing 14 machine types, with multiple distro definitions (poky, poky-lsb, poky-tiny) we build out a very large number of build artifacts (the average size is about a quarter terabyte of build artifacts). With this many artifacts, the QA task is herculean. The time needed to fix these issues would have pushed out an rc2 spin of M2 into the M3 time period, and this would have greatly impacted our QA effort on M3. As we've fixed these issues in master and as M3 is quickly approaching it made little sense to release something of limited utility. So, while I'm a bit disappointed that we've missed this milestone, it's actually a good thing, in that, a very vital piece of OE-Core was upreved early enough in the 1.5 cycle so that any issues that is caused can and will be resolved early. In the end, this will make 1.5 a better release. -b -- Elizabeth Flanagan Yocto Project Build and Release _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto