From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: update the dpdk 2.2 release notes
Date: Wed, 16 Sep 2015 14:58:36 +0200 [thread overview]
Message-ID: <1465261.rIY0HBKrif@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20233D44E@IRSMSX103.ger.corp.intel.com>
2015-09-16 10:50, Mcnamara, John:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > In order to easily read the release notes, I suggest to order items
> > logically, starting with API (ethdev, cryptodev), EAL, drivers, libs,
> > tools, examples.
> > Maybe that adding some subtitles would help.
> > Opinions?
>
> Hi
>
> I forget to do it with the above section but in the previous release notes I sorted the "Resolved Issues" alphabetically. It isn't a logical ordering but it is reasonably easy to navigate and understand:
>
> http://dpdk.org/doc/guides/rel_notes/release_2_1.html#resolved-issues
>
> Would that be sufficient?
To me, reading an alphabetically sorted list of fixes, is like reading
a random list: there is no real logic.
Grouping drivers together seems easier.
Other opinions?
Other people reading the release notes? ;)
next prev parent reply other threads:[~2015-09-16 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 13:07 John McNamara
2015-09-15 13:21 ` Thomas Monjalon
2015-09-16 10:50 ` Mcnamara, John
2015-09-16 12:58 ` Thomas Monjalon [this message]
2015-09-16 8:27 ` David Marchand
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=1465261.rIY0HBKrif@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--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).