From: Raslan Darawsheh <rasland@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "bluca@debian.org" <bluca@debian.org>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"Xueming(Steven) Li" <xuemingl@nvidia.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
"john.mcnamara@intel.com" <john.mcnamara@intel.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: RE: [PATCH v2] doc: update LTS maintenance to 3 years
Date: Tue, 23 Jan 2024 07:55:28 +0000 [thread overview]
Message-ID: <MN0PR12MB6056F217E94608690789BA6ECF742@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240117162419.223820-1-ktraynor@redhat.com>
Hi,
> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Wednesday, January 17, 2024 6:24 PM
> To: dev@dpdk.org
> Cc: bluca@debian.org; NBU-Contact-Thomas Monjalon (EXTERNAL)
> <thomas@monjalon.net>; david.marchand@redhat.com;
> christian.ehrhardt@canonical.com; Xueming(Steven) Li
> <xuemingl@nvidia.com>; ferruh.yigit@amd.com; john.mcnamara@intel.com;
> techboard@dpdk.org; Kevin Traynor <ktraynor@redhat.com>
> Subject: [PATCH v2] doc: update LTS maintenance to 3 years
>
> 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>
>
Acked-by: Raslan Darawsheh <rasland@nvidia.com>
Kindest regards
Raslan Darawsheh
next prev parent reply other threads:[~2024-01-23 7:55 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 [this message]
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
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=MN0PR12MB6056F217E94608690789BA6ECF742@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.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).