On Thu, 2013-04-04 at 14:09 -0300, Otavio Salvador wrote: > On Thu, Apr 4, 2013 at 12:41 PM, Saul Wold <s...@linux.intel.com> wrote: > > > > I am going to defer this to 1.5 when it opens up, I still need to review the > > recipe, but wanted to give you a heads up about the deferral. > > Any reasoning to defer it when it adds a good tool for validation and > test? It also offers very low risk of breaking something.
We're two weeks before release and meant to be bug fixing now, new features add risk. You say this patch is low risk but it will actually break builds. Why? It has machine specific code but isn't marked as machine specific and it will not work well in world builds for example. That is just the part I can spot from looking at it but it means its not been widely tested. Yes, we can fix these things but I really want to focus on the bugs we have right now, not fixing new code and adding new build failures. So Saul is right here in deferring this. Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
