From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yuanhan Liu Subject: Re: Suggestions for the dpdk stable tree Date: Mon, 23 May 2016 10:21:57 +0800 Message-ID: <20160523022157.GH5641@yliu-dev.sh.intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christian Ehrhardt , dev , Stephen Hemminger , Thomas Monjalon To: "Mcnamara, John" Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id D4005A10 for ; Mon, 23 May 2016 04:20:41 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, May 20, 2016 at 02:49:31PM +0000, Mcnamara, John wrote: > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Christian Ehrhardt > > Sent: Friday, May 20, 2016 9:07 AM > > To: dev ; Stephen Hemminger > > Subject: Re: [dpdk-dev] Suggestions for the dpdk stable tree > > > > Hi, > > I guess over time/releases less people mind the 2.2-stable. > > But I still see a lot of people referring to 2.2 - so why not giving this > > thread a ping again. > > > > ack / nack / opinions ? > > Hi Christian, > > We are interested in having a LTS/Stable tree. I didn't notice this thread, otherwise, I would have commented earlier: TBH, I have also thought of LTS tree few months before. But I was thinking, hmm, it's just a library, what's the big deal of maintaining a stable tree for it. I then hide it deep inside of my mind, silently. > We have been looking at identifying a maintainer and validation engineer internally to support the effort but haven't be able to finalize that. Once we do we will come back to the mailing list with a proposal and a request for comments. I would nominate myself as the LTS tree maintainer, if it makes sense to have one. > We would probably be looking at 16.04 or even 16.07 as the basis for the LTS at this stage. Just one opinion from the view of vhost: since 16.07 is a vhost ABI/API refactoring release, I'd suggest to base on 16.07, and then we could have less conflicts to apply later bug fix patches. However, I'm very open to choose any others as the base, say, even v2.2. --yliu > It would be great if we could get support from you or others as well. > > John. > -- >