From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-dev] [PATCH] doc/guides: mention 17.11 LTS in contributing/stable
Date: Thu, 2 Nov 2017 17:12:27 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EDEFF52@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20171031162855.5707-1-luca.boccassi@gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of
> luca.boccassi@gmail.com
> Sent: Tuesday, October 31, 2017 4:29 PM
> To: dev@dpdk.org
> Cc: thomas@monjalon.net; Luca Boccassi <bluca@debian.org>
> Subject: [dpdk-dev] [PATCH] doc/guides: mention 17.11 LTS in
> contributing/stable
>
> From: Luca Boccassi <bluca@debian.org>
>
> Signed-off-by: Luca Boccassi <bluca@debian.org>
> ---
> doc/guides/contributing/stable.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/doc/guides/contributing/stable.rst
> b/doc/guides/contributing/stable.rst
> index d52ec4772..0f2f1f375 100644
> --- a/doc/guides/contributing/stable.rst
> +++ b/doc/guides/contributing/stable.rst
> @@ -42,10 +42,10 @@ LTS Release
> -----------
>
> A stable release can be designated as an LTS release based on community -
> agreement and a commitment from a maintainer. An LTS release will have a -
> maintenance duration of 2 years.
> +agreement and a commitment from a maintainer. The current policy is
> +that each year's November release will be maintained as an LTS for 2
> years.
Strictly speaking we didn't agree that at Userspace. We said that we would evaluate
a 18.11 release next year. However, I am okay with this statement since it probably
reflects what the reality will be.
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2017-11-02 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 16:28 luca.boccassi
2017-11-02 17:12 ` Mcnamara, John [this message]
2017-11-12 4:39 ` 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=B27915DBBA3421428155699D51E4CFE23EDEFF52@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=luca.boccassi@gmail.com \
--cc=thomas@monjalon.net \
/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).