From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id AC2355F25 for ; Mon, 28 Jan 2019 15:27:35 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id A78C77F6B2; Mon, 28 Jan 2019 14:27:34 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (unknown [10.18.25.61]) by smtp.corp.redhat.com (Postfix) with ESMTPS id AEE74627DF; Mon, 28 Jan 2019 14:27:28 +0000 (UTC) From: Aaron Conole To: Thomas Monjalon Cc: Ferruh Yigit , Jay Rolette , "Mcnamara\, John" , "dev\@dpdk.org" , Jerin Jacob , Akhil Goyal , "Dumitrescu\, Cristian" , "Xu\, Qian Q" , Yongseok Koh , Maxime Coquelin , "Zhang\, Qi Z" , Shahaf Shuler , "De Lara Guarch\, Pablo" , "O'Hare\, Cathal" , Kevin Traynor , Timothy Redaelli References: <4043183.GGkcRsX4b2@xps> Date: Mon, 28 Jan 2019 09:27:27 -0500 In-Reply-To: <4043183.GGkcRsX4b2@xps> (Thomas Monjalon's message of "Sat, 26 Jan 2019 02:01:48 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Mon, 28 Jan 2019 14:27:35 +0000 (UTC) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 14:27:36 -0000 Thomas Monjalon writes: > 26/01/2019 00:37, Ferruh Yigit: >> On 1/25/2019 9:16 PM, Aaron Conole wrote: >> > Jay Rolette 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? I misunderstood the question I guess. I saw 'stable/LTS' and assumed it was lumping them together, sorry. Red Hat uses the LTS trees. We don't use the 'stable' tree (ie: Red Hat won't use 19.08.1). Kevin can correct me if i got something wrong here. > 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. I was under the impression that the instant (X+2).11 releases, X.11 is EOL. I guess that's for someone else to explain (maybe a candidate for something in doc/guides/.../release_cadence.rst to help clarify)?