From: Thomas Monjalon <thomas@monjalon.net>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dev@dpdk.org, christian.ehrhardt@canonical.com,
xuemingl@nvidia.com, bluca@debian.org
Subject: Re: [PATCH 2/2] doc: update LTS release cadence
Date: Tue, 11 Jan 2022 17:53:20 +0100 [thread overview]
Message-ID: <3141440.oiGErgHkdL@thomas> (raw)
In-Reply-To: <20211213164858.74244-2-ktraynor@redhat.com>
13/12/2021 17:48, Kevin Traynor:
> Regular LTS releases have previously aligned to DPDK main branch
> releases so that fixes being backported have already gone through
> DPDK main branch release validation.
>
> Now that DPDK main branch has moved to 3 releases per year, the LTS
> releases should continue to align with it and follow a similar release
> cadence.
>
> Update stable docs to reflect this.
>
> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
Series applied, thanks.
prev parent reply other threads:[~2022-01-11 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 16:48 [PATCH 1/2] maintainers: fix stable maintainers list Kevin Traynor
2021-12-13 16:48 ` [PATCH 2/2] doc: update LTS release cadence Kevin Traynor
2022-01-11 16:53 ` Thomas Monjalon [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=3141440.oiGErgHkdL@thomas \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=xuemingl@nvidia.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).