From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dan.rpsys.net ([93.97.175.187]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1UKXdp-0008Ug-K0; Tue, 26 Mar 2013 18:26:34 +0100 Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r2QHItW0028895; Tue, 26 Mar 2013 17:19:23 GMT X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net 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 iL8ZDO-nrbZE; Tue, 26 Mar 2013 17:19:23 +0000 (GMT) Received: from [192.168.3.10] (rpvlan0 [192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r2QHJI3V028910 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 26 Mar 2013 17:19:21 GMT Message-ID: <1364317761.3097.91.camel@ted> From: Richard Purdie To: yocto , openembedded-core , bitbake-devel , "poky@yoctoproject.org" Date: Tue, 26 Mar 2013 17:09:21 +0000 X-Mailer: Evolution 3.6.2-0ubuntu0.1 Mime-Version: 1.0 Subject: Yocto Project 1.5 Planning X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 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: Tue, 26 Mar 2013 17:26:34 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit We're now in the planning stages for the 1.5 release scheduled for about 6 months time. The process hasn't changed, if there are things you'd like to see worked on in this timeframe, please ensure there are entries for them in the bugzilla. Usually these are "enhancement" requests. https://bugzilla.yoctoproject.org/ We as a project will then go through these, decide on which ones to work on and at which priorities and then work through these in the 1.5 timeframe in the usual way. Obviously the project members do have some say in what they ultimately work on, equally I've always tried to ensure OE community priorities also get some attention and I'd say we have a pretty good track record there of getting things done. What I can say for sure is that if it isn't there, it is unlikely to get worked on. If you do plan to work on something yourself, it really does also help me and the team for it to be listed in there as I have some idea of when its coming and can for example make sure that we have enough runway for autobuilder testing and so on. It also means two people don't do the same thing! Cheers, Richard