From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ptmx.org (ptmx.org [178.63.28.110]) by mail.openembedded.org (Postfix) with ESMTP id 51B2571165 for ; Thu, 28 Aug 2014 07:18:51 +0000 (UTC) Received: from [192.168.178.14] (chello062178118086.5.14.vie.surfer.at [62.178.118.86]) by ptmx.org (Postfix) with ESMTPSA id D0EE0235CF for ; Thu, 28 Aug 2014 09:18:52 +0200 (CEST) Message-ID: <53FED7DC.6050707@pseudoterminal.org> Date: Thu, 28 Aug 2014 09:18:52 +0200 From: Carlos Rafael Giani User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: openembedded-core@lists.openembedded.org References: <1409210206.29296.129.camel@ted> In-Reply-To: <1409210206.29296.129.camel@ted> Subject: Re: 1.7 release feature freeze deadline this Friday X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2014 07:18:55 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 08/28/2014 09:16 AM, Richard Purdie wrote: > If you've been in the various calls or read the minutes you'd know about > this but it was mentioned to me that it has not been highlighted on the > mailing list. > > The M3 milestone close is the end of the week and this marks the feature > freeze point for the 1.7 release. We do have M4 after this but that is a > bug fixing and stabilisation milestone. > > There are some things I may still consider into M4, particular if > they're related to the stated objectives of the release, specifically > the developer workflow enhancements which is running behind schedule. As > time progresses, it will be increasingly unlikely things of that nature > will merge though. > > So if there are things you are after to see in 1.7 time is running out, > I at least need to be aware of them ASAP. > > Cheers, > > Richard > Has the GCC 4.9 situation been solved? At least Chromium was failing to build with it. Other packages were affected as well.