From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtprelay-h21.telenor.se ([195.54.99.196]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1RUG2s-0006pU-Tm for openembedded-devel@lists.openembedded.org; Sat, 26 Nov 2011 12:03:48 +0100 Received: from ipb5.telenor.se (ipb5.telenor.se [195.54.127.168]) by smtprelay-h21.telenor.se (Postfix) with ESMTP id BC709EAA43 for ; Sat, 26 Nov 2011 11:57:08 +0100 (CET) X-SENDER-IP: [83.227.56.19] X-LISTENER: [smtp.bredband.net] X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AncaAKbF0E5T4zgTPGdsb2JhbAAMOIlKoU4BAQEBN4IkAQEBAQM4QBELGAkWDwkDAgECAQ8iFBMGAgEBvhmHTYMVBJRKilaHNg X-IronPort-AV: E=Sophos;i="4.69,575,1315173600"; d="scan'208";a="3233939" Received: from c-1338e353.011-39-73746f12.cust.bredbandsbolaget.se (HELO [10.175.196.244]) ([83.227.56.19]) by ipb5.telenor.se with ESMTP; 26 Nov 2011 11:57:08 +0100 Message-ID: <4ED0C603.9020900@telia.com> Date: Sat, 26 Nov 2011 11:57:07 +0100 From: Ulf Samuelsson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15 MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <4ECD76E2.3040001@opendreambox.org> <0C757E680E33864AB113392C7E83F910BE5242@GSX300A.mxchg.m.corp> <1322134409.3391.21.camel@mattotaupa> In-Reply-To: Subject: Re: Plans for OE classic future X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Nov 2011 11:03:48 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 2011-11-25 23:04, Tom Rini wrote: > On Fri, Nov 25, 2011 at 12:31 AM, Frans Meulenbroeks > 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... > Won't it be a problem for existing projects, if you cannot add fixes to cope with new host OS versions. At the moment, openembedded-classic does not build properly with Ubuntu 11.10 . -- Best Regards Ulf Samuelsson