From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f68.google.com (mail-wr1-f68.google.com [209.85.221.68]) by dpdk.org (Postfix) with ESMTP id C0D67683E for ; Thu, 20 Dec 2018 09:02:31 +0100 (CET) Received: by mail-wr1-f68.google.com with SMTP id q18so680129wrx.9 for ; Thu, 20 Dec 2018 00:02:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:mime-version; bh=HYiC6w0rB3asMik+goxRzHkGh8r0SmYY4hyt+CsnRd0=; b=BexxQoor4O5y3hCePSiIC3h2fR0Z9MEXt6Frqo+o6AVj+Qf1AovKwKhgLQtHPEiYPj Ts6X8GTsDR+Lm7a92DLp0BHLTpuIwSOZ6Grgyx+6A5iNo72FBTn8msq6BC37vLULjNiB rsCUKJP7oJTsl1a9CVJZlUTJbJdbAEG08yC8XgHUFsOQfsX/YIhb01o1VKflIssHPVde b/UZ472Lu4x+cerIRxv7/gVpbGLlgFBdiuVClD7J8hwXVIpIzj+ILKKn2kPnqWBJYNXW jO6/VcuTDHOg5Ash58OUzBRN9USrmEA9Wem81AG47V7PhaF9Wd4NX3H8qKxcLDfaVp1c 736w== X-Gm-Message-State: AA+aEWYWSvrKcVqa9rZ/I5aE+f6SEcMyixcGHqgm4+1MUuQ7uVlSE409 Fj7rbA+L66gtc6PeOCfxlOc= X-Google-Smtp-Source: AFSGD/XVLHC7ZU/6d4ibKTM0lr5U7heQzpVa05b1VrqJUitpmyCxAuzrq9D34rsbOOHRQPN+GbM3bg== X-Received: by 2002:adf:92a4:: with SMTP id 33mr20958119wrn.11.1545292951322; Thu, 20 Dec 2018 00:02:31 -0800 (PST) Received: from localhost ([46.183.103.8]) by smtp.gmail.com with ESMTPSA id l6sm8654057wrv.70.2018.12.20.00.02.23 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 20 Dec 2018 00:02:30 -0800 (PST) Message-ID: <1545292928.9718.10.camel@debian.org> From: Luca Boccassi To: Ferruh Yigit , dev@dpdk.org, John McNamara , Marko Kovacevic Cc: Kevin Traynor , Yongseok Koh , Neil Horman Date: Thu, 20 Dec 2018 09:02:08 +0100 In-Reply-To: <20181219125253.77398-2-ferruh.yigit@intel.com> References: <20181219125253.77398-1-ferruh.yigit@intel.com> <20181219125253.77398-2-ferruh.yigit@intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Subject: Re: [dpdk-dev] [RFC 2/2] doc: add deprecation marker usage X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Dec 2018 08:02:31 -0000 On Wed, 2018-12-19 at 12:52 +0000, Ferruh Yigit wrote: > Define '__rte_deprecated' usage process. >=20 > Suggests keeping old API with '__rte_deprecated' marker until next > LTS. >=20 > Signed-off-by: Ferruh Yigit > --- > Cc: Luca Boccassi > Cc: Kevin Traynor > Cc: Yongseok Koh > Cc: Neil Horman > --- > =C2=A0doc/guides/contributing/versioning.rst | 9 +++++++++ > =C2=A01 file changed, 9 insertions(+) >=20 > diff --git a/doc/guides/contributing/versioning.rst > b/doc/guides/contributing/versioning.rst > index 19af56cd2..e0edd2e20 100644 > --- a/doc/guides/contributing/versioning.rst > +++ b/doc/guides/contributing/versioning.rst > @@ -128,6 +128,15 @@ added to the Release Notes: > =C2=A0=C2=A0=C2=A0these changes. Binaries using this library built prior = to version > 2.1 will > =C2=A0=C2=A0=C2=A0require updating and recompilation. > =C2=A0 > +New API replacing previous one > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +If a new API proposed functionally replaces an existing one, when > new API becomes > +active old one marked with ``__rte_deprecated`` until next LTS. In > next LTS API > +removed completely. > + Perhaps a bit of rephrasing, ie: "If a new API proposed functionally replaces an existing one, when the new API becomes active then the old one is marked with ``__rte_deprecated`` until the next LTS. In the next LTS, the API is removed completely." Other than that: Acked-by: Luca Boccassi --=20 Kind regards, Luca Boccassi