From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Kevin Traynor <ktraynor@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"David Marchand" <david.marchand@redhat.com>,
Luca Boccassi <bluca@debian.org>
Cc: "web@dpdk.org" <web@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-web] [PATCH v2] update latest LTS as 19.11
Date: Wed, 4 Dec 2019 14:05:03 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B07EE85BBA@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <9666270.atiki9bGxj@xps>
> -----Original Message-----
> From: web <web-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Wednesday, December 4, 2019 1:52 PM
> To: Kevin Traynor <ktraynor@redhat.com>; Yigit, Ferruh
> <ferruh.yigit@intel.com>; David Marchand <david.marchand@redhat.com>; Luca
> Boccassi <bluca@debian.org>
> Cc: web@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>
> Subject: Re: [dpdk-web] [PATCH v2] update latest LTS as 19.11
>
> 04/12/2019 14:44, Kevin Traynor:
> > On 04/12/2019 12:13, Ferruh Yigit wrote:
> > > Latest Stable\
> >
> > If the intention is to point it to the latest version of the latest
> > LTS, can we change it to 'Latest LTS'. I think it avoids some ambiguity,
> e.g.
> > if for some reason 20.02 was going to have a stable branch, it could
> > claim to be 'latest stable' too.
>
> Good question.
> What is the most interesting to highlight here?
> Latest LTS version or Latest stable version including short term?
>
>
My 2c. Latest LTS all the way! That's what we want to steer people towards.
next prev parent reply other threads:[~2019-12-04 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 12:06 [dpdk-web] [PATCH] " Ferruh Yigit
2019-12-04 12:13 ` [dpdk-web] [PATCH v2] " Ferruh Yigit
2019-12-04 12:58 ` Luca Boccassi
2019-12-04 13:01 ` Thomas Monjalon
2019-12-04 13:44 ` Kevin Traynor
2019-12-04 13:51 ` Thomas Monjalon
2019-12-04 14:05 ` Richardson, Bruce [this message]
2019-12-04 15:25 ` [dpdk-web] [PATCH v3] " Ferruh Yigit
2019-12-04 16:09 ` Kevin Traynor
2019-12-05 14:51 ` Thomas Monjalon
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=59AF69C657FD0841A61C55336867B5B07EE85BBA@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/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).