From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhall@mhcomputing.net>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170])
 by dpdk.org (Postfix) with ESMTP id 57EFA2BA8
 for <dev@dpdk.org>; Thu,  7 Apr 2016 23:52:14 +0200 (CEST)
Received: by mail.mhcomputing.net (Postfix, from userid 1000)
 id CF33E358; Thu,  7 Apr 2016 14:52:13 -0700 (PDT)
Date: Thu, 7 Apr 2016 14:52:13 -0700
From: Matthew Hall <mhall@mhcomputing.net>
To: Panu Matilainen <pmatilai@redhat.com>
Cc: Marc Sune <marcdevel@gmail.com>,
 Thomas Monjalon <thomas.monjalon@6wind.com>, dev@dpdk.org
Message-ID: <20160407215213.GB28667@mhcomputing.net>
References: <1610488.T03Kyi0Reo@xps13> <5911950.ZPQvAWoePl@xps13>
 <5706295A.3000406@redhat.com>
 <CA+3n-ToGtVRLXu2S8J2a14cDYHhfUDZixdAY3mM5xWtERbYh0Q@mail.gmail.com>
 <570649C7.2030709@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <570649C7.2030709@redhat.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [dpdk-dev] On DPDK ABI policy
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Apr 2016 21:52:14 -0000

On Thu, Apr 07, 2016 at 02:51:35PM +0300, Panu Matilainen wrote:
> LTS releases could help the situation somewhat, but then again
> people tend to still want those new fancy things backported (you
> know, have the cake and eat it too) but that can't be done because
> of ABI breakage, so they're forced to run the latest version anyway.

RH and Debian / Ubuntu don't put features in LTS except extremely rarely. 
Generally only if there's severe functionality breakage or security issues and 
the rest is ignored, and for good reason, as this is much more reliable and 
simple and predictable.

If people are so irrational they can't deal with that simple of a policy, 
NEXT_ABI, LTS, etc. is never going to help them.

If people like to have backported stuff, yes of course we can make trees and 
branches for this, they are basically free in Git. But at that point community 
people in need of LTS forks of features need to step up to the plate to help 
out.

Matthew.