From mboxrd@z Thu Jan 1 00:00:00 1970 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) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=oEubcl/upz3B819IepcAdSHRn2/JbRbCW2NmpO+jdIg=; b=PxhOAD5UfYf/q5s3/f4tPVQ48e3gwhTgnAhbOvwMwBdkwPUEj+7EiNNcb5R1W+2oEB 96+XwdFub/g8oJpAoe50+svVkYUbVv0MRWm2ZzzZV1wPKwcvbsUt9ASLgYI31Hh0qrA1 2mmWsMViSLcRWGFGnO/6FB4Rwdw75K4BvBtgy2sz7tz45K1UCEeNzyUhz+emtz3Sjl6D /JTlJa7U0DoUPlNIIDBcskC9HKu7VD7Z/uDLcMfG3imDHQ2PlVzPpLvIt/63nXJbnywk Xk7XwKmKO3yoyOum1IG5TN9s3na4MXYFWTB9hdF0JY0Ncdj77YJ6g3/pYPdOwAnlYFM3 jZ7A== X-Gm-Message-State: ALoCoQn3cn+Ffo8a/rX3QGbwjlp3sD/T8pmszcTkzxhR/T7oJjMEhxda+0J0yfhvlHktVGFmrbzd X-Received: by 10.180.23.71 with SMTP id k7mr18530587wif.11.1442408384383; Wed, 16 Sep 2015 05:59:44 -0700 (PDT) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by smtp.gmail.com with ESMTPSA id ww8sm26514903wjb.4.2015.09.16.05.59.43 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Sep 2015 05:59:43 -0700 (PDT) From: Thomas Monjalon To: "Mcnamara, John" Date: Wed, 16 Sep 2015 14:58:36 +0200 Message-ID: <1465261.rIY0HBKrif@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: <1442322474-27380-1-git-send-email-john.mcnamara@intel.com> <2874598.qVsS3oCtQ8@xps13> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] doc: update the dpdk 2.2 release notes X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Sep 2015 12:59:44 -0000 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? ;)