From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 6B9114C99 for ; Tue, 16 Oct 2018 11:18:48 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E650B221E9; Tue, 16 Oct 2018 05:18:47 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 16 Oct 2018 05:18:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=aoF52FYMyUjjrjlhjw9Lc7eSUz31LxOl/d0Qv3P7k3Y=; b=meffUWeOEboI STfMqGSKOXeZmMaH7n5Z+KdhIe1FdHiy7OXaLBLJ5YHp8h0RqbLI/CVn+p92RB/D lY9c/TJrs75wstypRXx+GHRsZqvjrejz5Rc3Tncv+62hh+CeHzLCVPRPcHmKEO4W uJa46FhjRw1OTb5SHxJSr8idMPY9vsU= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=aoF52FYMyUjjrjlhjw9Lc7eSUz31LxOl/d0Qv3P7k 3Y=; b=F4Y78KzJwsjMRz16/MvCVgjdOU6tK1k2FLLYOabXsgUR/dT5DjFLo+rH2 JbWLa3nMHn5yLZN6bnhkfuP0e53wKwmTkejf81ahyDRZqtm86BNjm2zmGbuuschf Z2f4SYLaZow1NhyT5hh4qPEGc4UP00vHlHsaD1/NDkjxtpcd2NRPN7i1hoJmEQ81 UVsYvOO1tNNsIZE+Z9WiU+psESNxpHJWhDf2lwFp6I4ysLyKeC3FwAEMvAEw1qHN vF8L+CE34aQww3URf0FC6fEuOGcKvO0TsKh8FHGhwzJv71n/GgpOI5RAwIpp0fmq ZCHSqrTCrZXxfJdNtrLDm8JLs2IzA== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id BFBB8E44DC; Tue, 16 Oct 2018 05:18:46 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: marko.kovacevic@intel.com, web@dpdk.org Date: Tue, 16 Oct 2018 11:18:48 +0200 Message-ID: <6401954.CyYEqp0Efv@xps> In-Reply-To: References: <20180912105908.22499-1-marko.kovacevic@intel.com> <6741340.EJca0k8ij8@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-web] [PATCH v4] update Intel roadmap for 18.11 X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2018 09:18:48 -0000 12/09/2018 18:47, Ferruh Yigit: > On 9/12/2018 5:20 PM, Thomas Monjalon wrote: > > 12/09/2018 17:10, Ferruh Yigit: > >> On 9/12/2018 1:41 PM, Thomas Monjalon wrote: > >>> From: Marko Kovacevic > >>> > >>> The NAT support was already integrated in DPDK 18.08. > >>> The new features were announced in the dpdk-dev mailing list: > >>> http://mails.dpdk.org/archives/dev/2018-August/109986.html > >>> > >>> Signed-off-by: Marko Kovacevic > >>> Acked-by: Thomas Monjalon > >> > >> Reviewed-by: Ferruh Yigit > >> > >>> v4: I have removed most of the upper-casing and words "add" and > >>> "support", in order to make it shorter. > >>> The items are also moved in order to keep the same kind of sorting > >>> we use in the releases notes (EAL, ethdev, crypto, other libs, apps). > >> > >> Those were copy-paste from Intel Roadmap mail, changing them adds confusion > >> about if they are same thing in Roadmap item or not and slows down the updates. > > > > Which change are you referring as adding confusion? > > - lowercase? > > - remove some verbs? > > - sorting list? > > changing wording, like > "Add Crypto Support to Packet Framework" to "crypto in Packet Framework". > > Concern is if someone, not familiar to feature, search an Intel roadmap item > won't have an exact match and may not be sure if they are same thing or not. > Over cautious? I think you are over cautious :) Applied