From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v4 3/3] doc: add deprecation marker usage Date: Thu, 31 Jan 2019 18:17:50 +0100 Message-ID: <3155698.1yX0fgTuye@xps> References: <20190122162310.53613-1-ferruh.yigit@intel.com> <20190124181019.17168-1-ferruh.yigit@intel.com> <20190124181019.17168-3-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, John McNamara , Marko Kovacevic , Luca Boccassi , Kevin Traynor , Yongseok Koh , Neil Horman To: Ferruh Yigit Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id A30F21B479 for ; Thu, 31 Jan 2019 18:17:54 +0100 (CET) In-Reply-To: <20190124181019.17168-3-ferruh.yigit@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 24/01/2019 19:10, Ferruh Yigit: > Define '__rte_deprecated' usage process. > > Suggests keeping old API with '__rte_deprecated' marker including > next LTS, they will be removed just after the LTS release. > > Signed-off-by: Ferruh Yigit > Acked-by: Luca Boccassi > Acked-by: Neil Horman [...] > +New API replacing previous one > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +If a new API proposed functionally replaces an existing one, when the new API > +becomes non-experimental then the old one is marked with ``__rte_deprecated``. > +Deprecated APIs removed completely just after the next LTS. APIs removed -> APIs are removed > + > +Reminder that new API should follow deprecation process to be able to replace old API. This last sentence is not clear to me. I think you mean the old API should follow deprecation process to be removed (replaced).