From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Liu, Yuanhan" <yuanhan.liu@intel.com>,
"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v1] doc: add guidelines on stable and lts releases
Date: Fri, 13 Jan 2017 13:14:17 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2026B0556@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1484312782-21120-1-git-send-email-john.mcnamara@intel.com>
> -----Original Message-----
> From: Mcnamara, John
> Sent: Friday, January 13, 2017 1:06 PM
> To: dev@dpdk.org
> Cc: Liu, Yuanhan <yuanhan.liu@intel.com>; thomas.monjalon@6wind.com;
> Mcnamara, John <john.mcnamara@intel.com>
> Subject: [PATCH v1] doc: add guidelines on stable and lts releases
>
> Add document explaining the current Stable and LTS process.
Hi,
Just a reminder that DPDK 16.07 was a stable release, 16.11 is a stable
release and it will also become the 2 year LTS release.
Some links:
http://dpdk.org/ml/archives/stable/ - Mailing list
http://dpdk.org/download - Download page for mainline and stable release
http://fast.dpdk.org/rel/ - Stable release tarballs
If you are a downstream consumer of DPDK and would like to influence how the
Stable/LTS releases are working, or should work, then let us know.
John
next prev parent reply other threads:[~2017-01-13 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 13:06 John McNamara
2017-01-13 13:14 ` Mcnamara, John [this message]
2017-01-13 16:29 ` Thomas Monjalon
2017-01-13 17:57 ` Mcnamara, John
2017-02-08 12:24 ` Thomas Monjalon
2017-01-20 8:43 Yuanhan Liu
2017-02-08 14:39 ` Thomas Monjalon
2017-02-28 7:13 ` Yuanhan Liu
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=B27915DBBA3421428155699D51E4CFE2026B0556@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=yuanhan.liu@intel.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).