DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
	dev@dpdk.org, dmitry.kozliuk@gmail.com
Subject: Re: [dpdk-dev] [PATCH v1] doc: update release notes for 21.02
Date: Fri, 12 Feb 2021 14:52:59 +0100	[thread overview]
Message-ID: <2955596.pFaKxuZ42Q@thomas> (raw)
In-Reply-To: <20210212133055.GB970@bricha3-MOBL.ger.corp.intel.com>

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.



  reply	other threads:[~2021-02-12 13:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 12:04 John McNamara
2021-02-11 12:08 ` Mcnamara, John
2021-02-11 23:33   ` Thomas Monjalon
2021-02-12  8:14     ` Dmitry Kozlyuk
2021-02-12 11:57     ` Bruce Richardson
2021-02-12 12:49       ` Thomas Monjalon
2021-02-12 13:30         ` Bruce Richardson
2021-02-12 13:52           ` Thomas Monjalon [this message]
2021-02-14  9:57 ` Thomas Monjalon

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=2955596.pFaKxuZ42Q@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=john.mcnamara@intel.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).