From: Kevin Traynor <ktraynor@redhat.com>
To: "Luca Boccassi" <bluca@debian.org>,
"Morten Brørup" <mb@smartsharesystems.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org, david.marchand@redhat.com,
christian.ehrhardt@canonical.com, xuemingl@nvidia.com,
ferruh.yigit@amd.com, john.mcnamara@intel.com,
techboard@dpdk.org
Subject: Re: [PATCH v2] doc: update LTS maintenance to 3 years
Date: Thu, 28 Mar 2024 10:25:38 +0000 [thread overview]
Message-ID: <6dc3ebb5-cf00-499f-a1ae-bccfbddca638@redhat.com> (raw)
In-Reply-To: <CAMw=ZnT7rVu3F2-RYLnjrNoV0i3QeW4XJNZW1vYegwB_bhka4A@mail.gmail.com>
On 28/03/2024 10:01, Luca Boccassi wrote:
> On Mon, 25 Mar 2024 at 10:02, Morten Brørup <mb@smartsharesystems.com> wrote:
>>
>>> From: Thomas Monjalon [mailto:thomas@monjalon.net]
>>> Sent: Monday, 25 March 2024 00.14
>>>
>>> 17/01/2024 17:24, Kevin Traynor:
>>>> The existing official policy was to maintain LTS releases for 2 years.
>>>>
>>>> 19.11 and 20.11 LTS releases were maintained for 3 years and there was
>>>> not significant issues caused by code divergence from main etc.
>>>>
>>>> Update the policy to indicate 3 years maintenance for LTS releases, but
>>>> note that it depends on community support.
>>>>
>>>> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
>>>
>>> More opinions, comments or acks?
>>
>> It is an improvement.
>>
>> Acked-by: Morten Brørup <mb@smartsharesystems.com>
>
> Acked-by: Luca Boccassi <bluca@debian.org>
>
Xueming/Christian - any comments on this ?
If it sounds ok, can you Ack ?
thanks,
Kevin.
prev parent reply other threads:[~2024-03-28 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 16:18 [PATCH] " Kevin Traynor
2024-01-17 16:24 ` [PATCH v2] " Kevin Traynor
2024-01-23 7:55 ` Raslan Darawsheh
2024-03-21 14:38 ` Mcnamara, John
2024-03-24 23:14 ` Thomas Monjalon
2024-03-25 10:02 ` Morten Brørup
2024-03-28 10:01 ` Luca Boccassi
2024-03-28 10:25 ` 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=6dc3ebb5-cf00-499f-a1ae-bccfbddca638@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=john.mcnamara@intel.com \
--cc=mb@smartsharesystems.com \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
--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).