On Fri, 2011-09-16 at 14:22 +0200, Eric Bénard wrote: > I don't understand why oe-core's development has to be stopped by yocto's > releases process but I may not have found the right page on the wiki > explaining all the details : may you please give me some links concerning > this > policy ?
It does seem a little bit strange, yes. If it's just a short period then I don't think there should be any real problem with granting yocto a short freeze in oe-core so that they can do their branching. Of course, this isn't going to scale very well if every user of oe-core starts asking for a development freeze so that they can cut their own release branches, and it isn't totally obvious to me that yocto couldn't just as easily have branched from some semi-arbitrary point and then cherry-picked or reverted a few changes to get to where they wanted. Possibly the intent is to make a standalone release of oe-core itself on the back of whatever yocto ends up shipping, I dunno. That seems like it might be a reasonable enough way to get a version of OE-core that other people can build on without having to repeat all the QA and release engineering work that yocto are presumably doing for themselves. But at the end of the day, I guess, it's Richard's tree and he is perfectly entitled to freeze it whenever he wishes. OE-core is still quite a young project and it seems sensible enough to try different things and see what works. p. _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
