From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Last call for deprecation notices
Date: Wed, 21 Nov 2018 11:45:47 +0000
Message-ID: <1f06e623-064d-0bb8-c194-37aa06388cbb@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Cc: Thomas Monjalon <thomas@monjalon.net>
To: dpdk-dev <dev@dpdk.org>
Return-path: <dev-bounces@dpdk.org>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
 by dpdk.org (Postfix) with ESMTP id 275435F44
 for <dev@dpdk.org>; Wed, 21 Nov 2018 12:45:49 +0100 (CET)
Content-Language: en-US
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>

If there are any planned API/ABI change on v19.02, deprecation notice patches
for them should be sent, approved and merged withing v18.11 scope which is only
a few days away.

If you will be working on a feature for v19.02, please take some time think if
it will cause any API/ABI change.
And if it will so, please send the deprecation notice for it ASAP, otherwise
your feature can be blocked for the release because of API/ABI breakage it causes.

Thanks,
ferruh