Executive Summary ================= 3.14 kernel is in and we have green builds. Managed to make a dent in the defect tracking metrics but work remains. Trending well for the release, need to keep up the bug fixing.
1.6 Release Status =============== The 3.14 kernel was released, we were able to updated the patches we had queued ready and it merged fairly smoothly. The builds last night after 3.14 was integrated were all green which is nice to see. This included the switch to the two new reference BSPs. This was a big risk factor for the release so its nice to see it happen smoothly, finally. I've started aggressively trying to sort out my bug backlog, I've managed to close about 10 of them over the past week, some were found not to be bugs when they were delved into, some were resolved. There are some interesting bugs to do with sstate reuse too. My remaining 6 bugs (ignoring enhancements) are probably 1.7 material at this point. I know others have been making an effort too, including in other areas like documentation. We still have some runway before release so lets use that time to best advantage and see if we can lower the bug tracking metrics further. I have been trying to merge bug fixes quickly. I have to say that there has been a sharp drop in quality of patches on the list over the last week though. As people rush to try and get things in, its clear less testing is happening and this puts the build at risk. I'm therefore starting to be quite strict on review and if something is rushed and buggy, it (and any subsequent versions) will move to the bottom of the priority list. Autobuilder =========== This seems to be stabilising. There has been the odd setup issue, another AB had RAID issues and the odd regression crept into the autobuilder code but things are being dealt with and feel under control. Bitbake Changes =============== There is still some churn on the toaster codebase but given its new code, that is probably only to be expected. There have been some useful sstate signature fixes merged. I'm particularly interested in reports from people where sstate should have been reused and it wasn't. I'd really like to get to the bottom of these issues once and for all. Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core