From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
John McNamara <john.mcnamara@intel.com>
Cc: David Marchand <david.marchand@redhat.com>,
dev@dpdk.org, Jerin Jacob <jerinj@marvell.com>,
dpdk-dev <dev@dpdk.org>, Akhil Goyal <gakhil@marvell.com>,
Declan Doherty <declan.doherty@intel.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Jan Viktorin <viktorin@rehivetech.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Ray Kinsella <mdr@ashroe.eu>,
Radha Mohan Chintakuntla <radhac@marvell.com>,
Veerasenareddy Burru <vburru@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Nalla Pradeep <pnalla@marvell.com>,
Ciara Power <ciara.power@intel.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Shijith Thotton <sthotton@marvell.com>,
Ashwin Sekhar T K <asekhar@marvell.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
Satananda Burla <sburla@marvell.com>,
Liron Himi <lironh@marvell.com>,
Jerin Jacob <jerinjacobk@gmail.com>,
Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v1] drivers: remove octeontx2 drivers
Date: Tue, 11 Jan 2022 17:58:01 +0100 [thread overview]
Message-ID: <37318384.10thIPus4b@thomas> (raw)
In-Reply-To: <4ae78b06-5143-0304-b2c6-03dffaeb0401@redhat.com>
07/12/2021 12:51, Kevin Traynor:
> On 07/12/2021 11:01, Ferruh Yigit wrote:
> > Not related with this set specifically, a more general question about updating
> > old release notes.
> > For me release notes should be frozen with the release and shouldn't be updated
> > at all afterwards, but there is no agreement on this and in practice old release
> > notes are updated.
> >
> > My question is, is there any benefit to keep a separate release notes file for
> > each release, and need to maintain old ones.
> > What about having a single release file, 'release.rst', and reset it after each
> > release?
> >
>
> I think there is a benefit to keeping them all - you can quickly
> look/grep through the files for multiple releases. e.g. if you wanted to
> check when a driver/feature was added etc. I agree it doesn't make sense
> to update them, unless there was a mistake at the time of release.
It makes sense to update old release notes, at least to make them compile.
Please remember we generate all of them as part of the guides:
https://doc.dpdk.org/guides/rel_notes/
next prev parent reply other threads:[~2022-01-11 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 8:35 jerinj
2021-12-06 13:35 ` Ferruh Yigit
2021-12-07 7:39 ` Jerin Jacob
2021-12-07 11:01 ` Ferruh Yigit
2021-12-07 11:51 ` Kevin Traynor
2022-01-11 16:58 ` Thomas Monjalon [this message]
2021-12-07 8:12 ` Akhil Goyal
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=37318384.10thIPus4b@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=asekhar@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=john.mcnamara@intel.com \
--cc=kirankumark@marvell.com \
--cc=ktraynor@redhat.com \
--cc=lironh@marvell.com \
--cc=mdr@ashroe.eu \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=pnalla@marvell.com \
--cc=radhac@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=sburla@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=sthotton@marvell.com \
--cc=vburru@marvell.com \
--cc=viktorin@rehivetech.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).