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>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 24/01/2018
Date: Sat, 26 Jan 2019 02:01:48 +0100 [thread overview]
Message-ID: <4043183.GGkcRsX4b2@xps> (raw)
In-Reply-To: <ac1a01e1-b6c6-0d85-146d-aab6e20c492f@intel.com>
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.
next prev parent reply other threads:[~2019-01-26 1:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 9:24 Mcnamara, John
2019-01-25 13:42 ` Jay Rolette
2019-01-25 16:40 ` Thomas Monjalon
2019-01-25 16:53 ` Jay Rolette
2019-01-25 17:05 ` Thomas Monjalon
2019-01-25 21:16 ` Aaron Conole
2019-01-25 23:37 ` Ferruh Yigit
2019-01-26 1:01 ` Thomas Monjalon [this message]
2019-01-28 14:27 ` Aaron Conole
2019-02-01 16:57 ` Mcnamara, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4043183.GGkcRsX4b2@xps \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=cathal.ohare@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rolette@infinite.io \
--cc=shahafs@mellanox.com \
--cc=tredaelli@redhat.com \
--cc=yskoh@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).