Re: [dpdk-dev] [PATCH v1] doc: update release notes for 21.02

[Thomas Monjalon <thomas@monjalon.net>]

12/02/2021 14:30, Bruce Richardson:
> On Fri, Feb 12, 2021 at 01:49:27PM +0100, Thomas Monjalon wrote:
> > 12/02/2021 12:57, Bruce Richardson:
> > > On Fri, Feb 12, 2021 at 12:33:35AM +0100, Thomas Monjalon wrote:
> > > > 11/02/2021 13:08, Mcnamara, John:
> > > > 
> > > > > Thomas,
> > > > > 
> > > > > I didn't remove the "Known Issues" section in case someone else
> > > > > adds something to it. If not you can remove it.
> > > > 
> > > > OK, I will remove.
> > > 
> > > Should the new dependency on pyelftools be called out here? Since it's
> > > not a common package I think it needs to be emphasised as a new
> > > dependency and instructions on how to get it.
> > 
> > What do you think of this update?  https://patches.dpdk.org/patch/87883/
> > 
> I think that is ok as an update for that particular section of "new
> features", but the fact is that that new feature introduces a new
> dependency for everyone, which means it may be missed for those who aren't
> interested in new features. Therefore, I think it should be called out
> somewhere else too, to really call attention to it. The reason I would
> suggest "known issues" is that it is a section that everyone looking at the
> release notes is likely to pay attention to. However, other options, such
> as a callout note at the top of the Release Notes i.e not in any particular
> section, might work as well.

I agree about the need,
but I don't think adding something in known issues is visible enough.
I will send a v2 with a note at the very beginning of the release notes.