I appreciate we're behind with 2.6 M4. I believe we're getting there however there are some things I still think need to be addressed:
* We need to merge the oeqa json test results reporting. Why? QA for the project is changing in 2.7 and we're going to be relying on automation very heavily. Having this in the next stable series (2.6) would massively assist with this work and lead to a better future for the project. * The checksum issues Mark highlighted are problems. Unfortunately the patches as proposed aren't working. * rootfs build time performance regression - Ross and I are simply out of time to look into this ourselves. This one will likely miss the release. * cmake changes - they're clearly important but currently break things and I'm worried whether we'd find all the problems if they merge. * any other fallout from the _remove change. Hopefully the queued patch fixes the problems we were seeing. * ptest regressions. I believe with master+openssl+valgrind patches we should be equivalent to rc2 results wise but its close run and there are still some tests failing which previously passed. There are also some decisions to make: * what to do with go versioning for 2.6. 1.11 is late but tempting given the problems with 1.10. I know a number of people are travelling for ELC-E which may further delay the release build but its ready when its ready... Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
