From: Kevin Traynor <ktraynor@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Yong Wang <wang.yong19@zte.com.cn>,
john.mcnamara@intel.com
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Luca Boccassi <bluca@debian.org>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] doc: fix typo in release note
Date: Tue, 21 May 2019 17:30:23 +0100 [thread overview]
Message-ID: <c1e9eb10-bad1-c364-3b29-4ad1bdc7d176@redhat.com> (raw)
In-Reply-To: <d2038eaf-30ea-b481-137a-348ea58c9d6b@intel.com>
On 21/05/2019 15:33, Ferruh Yigit wrote:
> On 5/21/2019 9:46 AM, Yong Wang wrote:
>> The patch fixes some typoes in 19.02 release note.
>>
>> Fixes: 6f04df497962 ("doc: add release notes for mlx5")
>> Fixes: bf9a90e2b562 ("doc: update release notes for 19.02")
>>
>> Signed-off-by: Yong Wang <wang.yong19@zte.com.cn>
>
> I am not in favor of updating old release notes, I believe the release notes is
> valid in the context of the release, so I am for keeping them as they released
> (with all their faults).
> Although we updated them in the past, and I don't have strong opinion on this,
> but lets take this as -1 from my side.
>
> Btw, while thinking perhaps this make sense for stable trees, I don't know if
> stable releases has the release notes?
> @Kevin, @Luca,
> As far as I can see LTS 16.11 & 17.11 updates the release notes with the fixed
> commits, but this is not done by 18.11.
> And update is only on commits it has, can any release notes update fix be merged
> into stable tree?
>
It's a good question, chatted with Ferruh on IRC. I think mistakes in
the release notes can be backported fine.
The other case is if someone adds a note in 19.05 release notes as part
of a fix that is backported to 18.11. Then it's more tricky because it
won't apply to 18.11 release notes and it is not what was tested in
Tested Platforms from the original release.
One option is to add another additional section for for each stable
release (in addition to the bugfix and validation list) for new notes.
Of course it means manual editing, or dedicated backports, so I'm not
really sure if it's worth the effort or not but it should be a rare event.
next prev parent reply other threads:[~2019-05-21 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 8:46 Yong Wang
2019-05-21 14:33 ` Ferruh Yigit
2019-05-21 16:30 ` Kevin Traynor [this message]
2019-07-30 11:24 ` Mcnamara, John
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=c1e9eb10-bad1-c364-3b29-4ad1bdc7d176@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--cc=wang.yong19@zte.com.cn \
--cc=yskoh@mellanox.com \
/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).