From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>, <dev@dpdk.org>,
"Kevin Traynor" <ktraynor@redhat.com>
Cc: <bluca@debian.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: Mon, 25 Mar 2024 11:02:05 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F329@smartserver.smartshare.dk> (raw)
In-Reply-To: <47539685.XUcTiDjVJD@thomas>
> 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>
next prev parent reply other threads:[~2024-03-25 10:02 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 [this message]
2024-03-28 10:01 ` Luca Boccassi
2024-03-28 10:25 ` Kevin Traynor
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=98CBD80474FA8B44BF855DF32C47DC35E9F329@smartserver.smartshare.dk \
--to=mb@smartsharesystems.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=ktraynor@redhat.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).