From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 37DB1711AB for ; Thu, 28 Aug 2014 14:24:01 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id s7SEO0lT022874; Thu, 28 Aug 2014 15:24:00 +0100 Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nELNw-BYH1Rj; Thu, 28 Aug 2014 15:24:00 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id s7SENtWW022871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 28 Aug 2014 15:23:57 +0100 Message-ID: <1409235837.29296.143.camel@ted> From: Richard Purdie To: Carlos Rafael Giani Date: Thu, 28 Aug 2014 15:23:57 +0100 In-Reply-To: <53FED7DC.6050707@pseudoterminal.org> References: <1409210206.29296.129.camel@ted> <53FED7DC.6050707@pseudoterminal.org> X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Cc: openembedded-core@lists.openembedded.org 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 14:24:05 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2014-08-28 at 09:18 +0200, Carlos Rafael Giani wrote: > 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. We merged in various gcc updates including a fix for the infamous kernel bug afaik. I don't know the situation with chromium but that did sound like a chromium issue rather than gcc... If we're missing patches to gcc please do shout out but I'm not seeing bugs which suggest we should default back to 4.8 at this point. Cheers, Richard