On Fri, Nov 25, 2011 at 12:31 AM, Frans Meulenbroeks <fransmeulenbro...@gmail.com> wrote:
> After all, isn't one of the purposes of OE to promote information sharing, > cooperation and the use of openembedded technology (and not make things > harder). One of the points of making master read-only would be to ensure that changes aren't lost. Perhaps the transition needs to be: - master is as it is today - master becomes oe-core backport || master-only bugfixes only - master becomes read only. And we go from the first step to the second step sometime sooner rather than later. The top of my head date would be before the paid-developers go on end of year breaks to try and make sure all the hobbyist folks start their hacking with oe-core+etc rather than master and risk getting caught later. I'm open to arguments on why that's exactly backwards... -- Tom _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
