From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v2] config: disable RTE_NEXT_ABI by default
Date: Thu, 04 Oct 2018 17:55:34 +0200
Message-ID: <33456122.koQSlajCb5@xps>
References: <20181004154306.65867-1-ferruh.yigit@intel.com>
 <1785611.eL8Z1dKoq2@xps> <56a42359-9ead-7c33-72a3-1d89d56f383c@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, Neil Horman <nhorman@tuxdriver.com>,
 Luca Boccassi <bluca@debian.org>,
 Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com
 [64.147.123.25]) by dpdk.org (Postfix) with ESMTP id B36EA1B556
 for <dev@dpdk.org>; Thu,  4 Oct 2018 17:55:39 +0200 (CEST)
In-Reply-To: <56a42359-9ead-7c33-72a3-1d89d56f383c@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

04/10/2018 17:28, Ferruh Yigit:
> On 10/4/2018 4:10 PM, Thomas Monjalon wrote:
> > 04/10/2018 17:48, Ferruh Yigit:
> >> Enabling RTE_NEXT_ABI means to enable APIs that break the ABI for
> >> the current release and these APIs are targeted for further release.
> > 
> > It seems nobody is using it in last releases.
> > 
> >> RTE_NEXT_ABI shouldn't be enabled by default.
> > 
> > The reason for having it enabled by default is that when you build DPDK
> > yourself, you probably want the latest features.
> > If packaged properly for stability, it is easy to disable it in
> > the package recipe.
> 
> My concern was (if this has been used), user may get unstable APIs and without
> explicitly being aware of it.

I am OK with both defaults (enabled or disabled).