From: "Morten Brørup" <mb@smartsharesystems.com>
To: <dev@dpdk.org>
Subject: Deprecation Notices history
Date: Tue, 25 Jul 2023 11:47:22 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87A84@smartserver.smartshare.dk> (raw)
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ørup
reply other threads:[~2023-07-25 9:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=98CBD80474FA8B44BF855DF32C47DC35D87A84@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).