From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 7C7C842F42;
	Tue, 25 Jul 2023 11:47:25 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 08D5040A7F;
	Tue, 25 Jul 2023 11:47:25 +0200 (CEST)
Received: from dkmailrelay1.smartsharesystems.com
 (smartserver.smartsharesystems.com [77.243.40.215])
 by mails.dpdk.org (Postfix) with ESMTP id F38B540697
 for <dev@dpdk.org>; Tue, 25 Jul 2023 11:47:23 +0200 (CEST)
Received: from smartserver.smartsharesystems.com
 (smartserver.smartsharesys.local [192.168.4.10])
 by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id E06E5205EF
 for <dev@dpdk.org>; Tue, 25 Jul 2023 11:47:22 +0200 (CEST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Deprecation Notices history
Date: Tue, 25 Jul 2023 11:47:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87A84@smartserver.smartshare.dk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Deprecation Notices history
Thread-Index: Adm+3QJdRngaUgvuQCGdodYaoTQWnQ==
From: =?iso-8859-1?Q?Morten_Br=F8rup?= <mb@smartsharesystems.com>
To: <dev@dpdk.org>
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
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

Why are Deprecation Notices not part of the Release Notes?

If a DPDK developer wants to upgrade his application from e.g. 20.11 to =
22.11, it might be informative to review the historical Deprecation =
Notices.

Is it because we promise that (when the announced change actually =
occurs) the deleted Deprecation Notice entry is replaced by a Release =
Note entry?

Anyway, I think that historical Deprecation Notices should be publicly =
available on the web site and/or with the Release Notes, and not only =
available in the GIT log.


Med venlig hilsen / Kind regards,
-Morten Br=F8rup