[dpdk-dev] [PATCH] doc: update the dpdk 2.2 release notes

Thomas Monjalon thomas.monjalon at 6wind.com
Wed Sep 16 14:58:36 CEST 2015


2015-09-16 10:50, Mcnamara, John:
> From: Thomas Monjalon [mailto:thomas.monjalon at 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? ;)



More information about the dev mailing list