From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: [PATCH v5 3/3] doc: add deprecation marker usage Date: Fri, 1 Mar 2019 17:32:50 +0000 Message-ID: <20190301173250.80930-3-ferruh.yigit@intel.com> References: <20190124181019.17168-1-ferruh.yigit@intel.com> <20190301173250.80930-1-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: Luca Boccassi , Neil Horman , Kevin Traynor , Yongseok Koh To: dev@dpdk.org, John McNamara , Marko Kovacevic Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 908654C90 for ; Fri, 1 Mar 2019 18:33:01 +0100 (CET) In-Reply-To: <20190301173250.80930-1-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" 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 --- Cc: Luca Boccassi Cc: Kevin Traynor Cc: Yongseok Koh Cc: Neil Horman v2: * Rephrased as commented v3: * changed when to remove the deprecated API. It is now just after an LTS release, the motivation is to keep changes small in LTS. Based on techboard discussion: http://mails.dpdk.org/archives/dev/2019-January/123519.html v4: change working around 'active': s/active/non-experimental/ s/become active/be able to replace old API v5: Grammar fix Rephrase API removal reminder --- doc/guides/contributing/versioning.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/guides/contributing/versioning.rst b/doc/guides/contributing/versioning.rst index 2fcb8bafd..30f8735ba 100644 --- a/doc/guides/contributing/versioning.rst +++ b/doc/guides/contributing/versioning.rst @@ -125,6 +125,15 @@ added to the Release Notes: these changes. Binaries using this library built prior to version 2.1 will require updating and recompilation. +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 are removed completely just after the next LTS. + +Reminder that old API should follow deprecation process to be removed. + Experimental APIs ----------------- -- 2.20.1