From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com
 [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 1BC25235
 for <dev@dpdk.org>; Sat, 26 Jan 2019 02:01:55 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 9FBD620F5C;
 Fri, 25 Jan 2019 20:01:54 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163])
 by compute1.internal (MEProxy); Fri, 25 Jan 2019 20:01:54 -0500
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=+cp6tcTgsfnpVHlTuot23EwMvoA4Z+AWLz5/37O4WIg=; b=VALpu2JP88BC
 r2YOtcL68eK3KazDIfezsy7jms6W00JF0zBjR4658cexNzNu7EUCByWIuwb79DLN
 M8o7M13sIKHYFsMUmMpDlIStKtIqIWG7z0utVgA8Z6W38zYuRmA3SaJIi8xt/JIs
 6U/niSK0Mfx4Klc3CkFHc3dCqi4pv+U=
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=+cp6tcTgsfnpVHlTuot23EwMvoA4Z+AWLz5/37O4W
 Ig=; b=I6RUo/aVvomGGYdE5uSbFjojZlImloIbXTllF+VlhinoPIcnPq1tJjnop
 BiURZT3ItQbnEHovCmBatC/OlmcrfIN0JPwryPxdyG7WUBIo4uKWVbBAhZi1YkVg
 iLQ7bXgRz3q40exlWKxjRAGJNwDwXEaIfBOGHRyY7QnIWc2m3ltVmn1MJm4LDoLE
 TYJA/1SWX3SrVgWImGlFoN45eZ7xWNhX+skX6m2xnyl+Mi9394DUVwFtCQ85kBfy
 T4vOmBIxKMktTY07UeTztGnV7hQEZX7Cvd37Y3H+B+WeSkzDtAGyzxN15cIC4kcL
 EcKhClwMvyXaWZMjGZvF3yx2EaXRw==
X-ME-Sender: <xms:gLFLXLBC_hhNJPKgyKq287OjMdG-izJ02RYOPVPkjeaGa10l-WAKIA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrieehgddvkecutefuodetggdotefrodftvf
 curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt
 tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufffkfgjfh
 gggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceo
 thhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppeejjedrudefgedrvddtfe
 drudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhho
 nhdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:gLFLXHqBDZYLQGH9gBBQHexasldVP5Npv5EvAeonLkwhOM57QjKnnA>
 <xmx:gLFLXDOR8yYOwoyyfcTQt-N8j56QWlZWU5MIOFTRgeKZ5HJbuSIEwA>
 <xmx:gLFLXKKataHu07nf_HrVANkUcaYuuVEhI5EN-ylD8_h129-gKqYtGw>
 <xmx:grFLXChnaYANR4-8PsIF73svSvR00jwrsCOe2T9T25ezAJb3hVIdjw>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 6FD8410087;
 Fri, 25 Jan 2019 20:01:49 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>, Aaron Conole <aconole@redhat.com>
Cc: Jay Rolette <rolette@infinite.io>, "Mcnamara,
 John" <john.mcnamara@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
 Jerin Jacob <jerin.jacob@caviumnetworks.com>,
 Akhil Goyal <akhil.goyal@nxp.com>, "Dumitrescu,
 Cristian" <cristian.dumitrescu@intel.com>, "Xu, Qian Q" <qian.q.xu@intel.com>,
 Yongseok Koh <yskoh@mellanox.com>,
 Maxime Coquelin <maxime.coquelin@redhat.com>, "Zhang,
 Qi Z" <qi.z.zhang@intel.com>, Shahaf Shuler <shahafs@mellanox.com>,
 "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>, "O'Hare,
 Cathal" <cathal.ohare@intel.com>, Kevin Traynor <ktraynor@redhat.com>,
 Timothy Redaelli <tredaelli@redhat.com>
Date: Sat, 26 Jan 2019 02:01:48 +0100
Message-ID: <4043183.GGkcRsX4b2@xps>
In-Reply-To: <ac1a01e1-b6c6-0d85-146d-aab6e20c492f@intel.com>
References: <B27915DBBA3421428155699D51E4CFE23F512773@IRSMSX103.ger.corp.intel.com>
 <f7timycsajc.fsf@dhcp-25.97.bos.redhat.com>
 <ac1a01e1-b6c6-0d85-146d-aab6e20c492f@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 24/01/2018
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Jan 2019 01:01:55 -0000

26/01/2019 00:37, Ferruh Yigit:
> On 1/25/2019 9:16 PM, Aaron Conole wrote:
> > Jay Rolette <rolette@infinite.io> writes:
> > 
> >>>    * Questions from Intel Test about the use of the Stable Tree.
> >>>      Do people use it? Each stable/LTS release requires a lot of
> >>>      testing and there are currently 3 releases to be tested.
> >>
> >> We do @ infinite io.
> > 
> > +1.  Red Hat also uses the LTS releases.
> 
> I assume the question is around stable tree, not LTS.
> We have LTS trees: 16.11, 17.11, 18.11
> And a stable tree valid for one release, latest stable tree will be: 18.08.x
> 
> In the existence of the LTS, do we need to keep stable tree?

Not sure to understand this question.
Yes we need 18.08.1 which is supposed to be more stable than 18.11.0.

> > I'm curious why there are three?
> > Isn't 16.11 deprecated now that 18.11 is released?  Maybe I
> > misunderstand that part.
> 
> 16.11 will have latest release and later EOL. For one release there are three
> LTS, other times two.

16.11.9 was supposed to be tested and released before 18.11.1.
The plan was to have only 2 LTS at a time.