From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by dpdk.org (Postfix) with ESMTP id 6E31BC33E for ; Fri, 20 May 2016 23:02:15 +0200 (CEST) X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id D19FDABB2; Fri, 20 May 2016 21:02:14 +0000 (UTC) To: Christian Ehrhardt , "Mcnamara, John" References: Cc: dev , Stephen Hemminger From: Markos Chandras Message-ID: <573F7B55.8050301@suse.de> Date: Fri, 20 May 2016 22:02:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] Suggestions for the dpdk stable tree X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 May 2016 21:02:15 -0000 Hi, On 05/20/2016 04:54 PM, Christian Ehrhardt wrote: > Hi, > it would be great to have an actively maintained LTS release. > > Clearly all us "Distribution People" like Panu, Me and a few others should > - whenever bugs are identified as potential backports - start the > discussion. > And having an stable-maintainer on the other end sounds great. > > The active maintainer you provide would do the usual auto-backport of fixes > once they come up upstream. > While us others would provide input from real exposure to users that flows > in via bug tracking tools. > > Looking forward for you coming back to the list once you have found one. Yes that sounds like a very good idea indeed! -- markos SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg