From: David Marchand <david.marchand@redhat.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dev <dev@dpdk.org>, "Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
Luca Boccassi <bluca@debian.org>,
Thomas Monjalon <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add link to stable roadmap
Date: Thu, 19 Mar 2020 09:33:08 +0100 [thread overview]
Message-ID: <CAJFAV8z9nXp0DU5TL76oTEMY0KP+71Bkfg66LJ+iEiccdpAuaA@mail.gmail.com> (raw)
In-Reply-To: <20200313195442.6375-1-ktraynor@redhat.com>
On Fri, Mar 13, 2020 at 8:55 PM Kevin Traynor <ktraynor@redhat.com> wrote:
>
> The versions currently listed as maintained have gone stale.
>
> Rather than having to keep updating this doc, point to the
> dpdk.org stable roadmap.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> ---
> doc/guides/contributing/stable.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/contributing/stable.rst b/doc/guides/contributing/stable.rst
> index 90b3d8e44..390452aa2 100644
> --- a/doc/guides/contributing/stable.rst
> +++ b/doc/guides/contributing/stable.rst
> @@ -63,5 +63,6 @@ fixes. Releases should be coordinated with the validation engineers to ensure
> that a tagged release has been tested.
>
> -The current maintained LTS branches are 17.11 and 18.11.
> +For a list of the currently maintained stable/LTS branches please see the
> +latest `stable roadmap <https://core.dpdk.org/roadmap/#stable>`_.
>
> At the end of the 2 years, a final X.11.N release will be made and at that
> --
> 2.21.1
>
Acked-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
next prev parent reply other threads:[~2020-03-19 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 19:54 Kevin Traynor
2020-03-19 8:33 ` David Marchand [this message]
2020-05-19 14:10 ` 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=CAJFAV8z9nXp0DU5TL76oTEMY0KP+71Bkfg66LJ+iEiccdpAuaA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=marko.kovacevic@intel.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).