From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] doc: update the dpdk 2.2 release notes Date: Wed, 16 Sep 2015 14:58:36 +0200 Message-ID: <1465261.rIY0HBKrif@xps13> References: <1442322474-27380-1-git-send-email-john.mcnamara@intel.com> <2874598.qVsS3oCtQ8@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Mcnamara, John" Return-path: Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by dpdk.org (Postfix) with ESMTP id A7426902 for ; Wed, 16 Sep 2015 14:59:44 +0200 (CEST) Received: by wicfx3 with SMTP id fx3so69336671wic.0 for ; Wed, 16 Sep 2015 05:59:44 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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? ;)