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 1SPFkC-0001Jd-EE for openembedded-devel@openembedded.org; Tue, 01 May 2012 18:16:04 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q41FoPHi015328; Tue, 1 May 2012 16:50:25 +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 15117-01; Tue, 1 May 2012 16:50:21 +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 q41FoEaB015322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 May 2012 16:50:16 +0100 Message-ID: <1335887416.7415.125.camel@ted> From: Richard Purdie To: openembedded-devel , openembedded-core , yocto Date: Tue, 01 May 2012 16:50:16 +0100 X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Subject: 1.3 Planning Process 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: Tue, 01 May 2012 16:16:04 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit I just wanted to highlight that the planning process for the next Yocto Project release (tentatively '1.3') is well under way now. I sent out a previous email about this but this is a quick reminder. We use the bugzilla (bugzilla.yoctoproject.org) to track proposed ideas and these will ultimately end up on https://wiki.yoctoproject.org/wiki/Yocto_1.3_Features as in previous releases as we work through the planning process. The aims and objectives for the next release are listed there (Continuity / Refresh, Continuity / Refresh and Usability). I can't promise things listed will happen or in what time frame but I do know if they're not there, they're much less likely to happen! :) Alternatively if anyone does want to discuss the future direction of the project(s), now is a good time to do it. Whilst I'm copying various lists, I'd suggest this discussion happens on OE-Core unless the question is clearly more appropriate elsewhere. Cheers, Richard