From: Kevin Traynor <ktraynor@redhat.com>
To: Pankaj Darak <pankajd@xilinx.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-stable] Git branch/tag for DPDK 19.11.0 LTS
Date: Wed, 12 Feb 2020 19:22:20 +0000 [thread overview]
Message-ID: <f0398199-e4ba-dfaf-1b10-fcbb90cb8c4c@redhat.com> (raw)
In-Reply-To: <CH2PR02MB6508F7C8ED31E23A27A50060CC180@CH2PR02MB6508.namprd02.prod.outlook.com>
On 11/02/2020 12:26, Pankaj Darak wrote:
> Hi,
>
> Is DPDK 19.11.0 being maintained as LTS?
Yes, Luca (cc) is the maintainer.
> If so, when the Git branch/tag for dpdk-stable-19.11.0 will be available on https://git.dpdk.org/dpdk-stable/?
fyi -
http://inbox.dpdk.org/stable/31aed464aa917104b0a57c6a32870e67a15a60ba.camel@gmail.com/
> If not, can you let me know which DPDK version is preferred to choose for LTS?
>
You can see the LTS's and their lifecycles here,
http://core.dpdk.org/roadmap/#stable
You have a choice of 18.11 or 19.11. Unless you have some specific
reason to pick 18.11, then 19.11 would be best as it will be maintained
for longer into the future.
> Regards,
> Pankaj
> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
>
prev parent reply other threads:[~2020-02-12 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 12:26 Pankaj Darak
2020-02-12 19:22 ` Kevin Traynor [this message]
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=f0398199-e4ba-dfaf-1b10-fcbb90cb8c4c@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=pankajd@xilinx.com \
--cc=stable@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).