From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SKYQ2-0006fI-Rw for openembedded-core@lists.openembedded.org; Wed, 18 Apr 2012 19:11:51 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3IH2MaF004208; Wed, 18 Apr 2012 18:02:22 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 04179-01; Wed, 18 Apr 2012 18:02:17 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3IH2EC6004201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Apr 2012 18:02:15 +0100 Message-ID: <1334768537.24091.156.camel@ted> From: Richard Purdie To: Patches and discussions about the oe-core layer Date: Wed, 18 Apr 2012 18:02:17 +0100 In-Reply-To: References: <1334760467.24091.100.camel@ted> <20120418145330.GM3635@jama.jama.net> <1334762445.24091.110.camel@ted> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: yocto Subject: Re: Yocto Project 1.2 Release Status X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2012 17:11:51 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2012-04-18 at 09:22 -0700, Chris Larson wrote: > On Wed, Apr 18, 2012 at 8:20 AM, Richard Purdie > wrote: > > On Wed, 2012-04-18 at 16:53 +0200, Martin Jansa wrote: > >> On Wed, Apr 18, 2012 at 03:47:47PM +0100, Richard Purdie wrote: > >> > I thought I'd update everyone with the current 1.2 status. > >> > > >> > I'm going to branch master for release at this point. We've fixed a lot > >> > of issues, I'm hoping the -rc4 build will be a good one. There are signs > >> > there are some more minor issues around and bugs do keep getting opened. > >> > These are still being investigated so we'll continue to let that happen. > >> > Once we have a QA report for -rc4, we'll be in a better position to make > >> > a call on how things are looking. > >> > >> Does it mean that after creating branch, master will be open for > >> postponed patches from ML and master-next or do you want to keep master > >> as close to release branch as possible for some time (e.g. for those > >> 1.2.1 fixes)? > > > > I have hoped people would work more on the stabilisation and testing but > > I don't think I'll be able to hold off the pressure to start master > > rolling again at some point relatively soon. > > Just because people have things to push or are pushing things which > aren't bugfixes doesn't mean their time is being taken up by anything > but stabilization right now. Your statement implies that everything > being pushed is being currently worked on, which is incorrect. I'm > sure Mentor isn't the only company with a backlog of already complete > local changes to get upstream.. So you're saying Mentor has been working on stabilization and has a queue of bugfixes which they've not shared? This doesn't help us much with the quality of this release :/ At least the next one might benefit I guess assuming you can resolve that backlog problem... Cheers, Richard From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tim.rpsys.net (93-97-173-237.zone5.bethere.co.uk [93.97.173.237]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id C7E12E013A6 for ; Wed, 18 Apr 2012 10:02:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3IH2MaF004208; Wed, 18 Apr 2012 18:02:22 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 04179-01; Wed, 18 Apr 2012 18:02:17 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q3IH2EC6004201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 18 Apr 2012 18:02:15 +0100 Message-ID: <1334768537.24091.156.camel@ted> From: Richard Purdie To: Patches and discussions about the oe-core layer Date: Wed, 18 Apr 2012 18:02:17 +0100 In-Reply-To: References: <1334760467.24091.100.camel@ted> <20120418145330.GM3635@jama.jama.net> <1334762445.24091.110.camel@ted> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: yocto Subject: Re: [OE-core] Yocto Project 1.2 Release Status X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2012 17:02:27 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Wed, 2012-04-18 at 09:22 -0700, Chris Larson wrote: > On Wed, Apr 18, 2012 at 8:20 AM, Richard Purdie > wrote: > > On Wed, 2012-04-18 at 16:53 +0200, Martin Jansa wrote: > >> On Wed, Apr 18, 2012 at 03:47:47PM +0100, Richard Purdie wrote: > >> > I thought I'd update everyone with the current 1.2 status. > >> > > >> > I'm going to branch master for release at this point. We've fixed a lot > >> > of issues, I'm hoping the -rc4 build will be a good one. There are signs > >> > there are some more minor issues around and bugs do keep getting opened. > >> > These are still being investigated so we'll continue to let that happen. > >> > Once we have a QA report for -rc4, we'll be in a better position to make > >> > a call on how things are looking. > >> > >> Does it mean that after creating branch, master will be open for > >> postponed patches from ML and master-next or do you want to keep master > >> as close to release branch as possible for some time (e.g. for those > >> 1.2.1 fixes)? > > > > I have hoped people would work more on the stabilisation and testing but > > I don't think I'll be able to hold off the pressure to start master > > rolling again at some point relatively soon. > > Just because people have things to push or are pushing things which > aren't bugfixes doesn't mean their time is being taken up by anything > but stabilization right now. Your statement implies that everything > being pushed is being currently worked on, which is incorrect. I'm > sure Mentor isn't the only company with a backlog of already complete > local changes to get upstream.. So you're saying Mentor has been working on stabilization and has a queue of bugfixes which they've not shared? This doesn't help us much with the quality of this release :/ At least the next one might benefit I guess assuming you can resolve that backlog problem... Cheers, Richard