DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: "Xueming Li" <xuemingl@nvidia.com>,
	"Luca Boccassi" <bluca@debian.org>,
	"Morten Brørup" <mb@smartsharesystems.com>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"christian.ehrhardt@canonical.com"
	<christian.ehrhardt@canonical.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: Thu, 6 Jun 2024 10:22:21 +0100	[thread overview]
Message-ID: <5722f9b2-9392-4f45-9e55-1564800dd6f3@redhat.com> (raw)
In-Reply-To: <DM4PR12MB53733C1C5BB9DA4C77D0D55DA1F42@DM4PR12MB5373.namprd12.prod.outlook.com>

On 23/05/2024 10:15, Xueming Li wrote:
> LGTM
> 
> Acked-by: Xueming Li <xuemingl@nvidia.com>
> ________________________________
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Thursday, May 23, 2024 5:12 PM
> To: Luca Boccassi <bluca@debian.org>; Morten Brørup <mb@smartsharesystems.com>
> Cc: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>; dev@dpdk.org <dev@dpdk.org>; david.marchand@redhat.com <david.marchand@redhat.com>; christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com>; Xueming 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
> 
> Ping Xueming/Christian,
> 
> Any comment on this, can you ack if you think it's a good idea ?
> 
> On 28/03/2024 10:25, Kevin Traynor wrote:
>> 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.
>>
>>
>>
> 
> 

Summarizing the Acks on this patch...

This has Acks from reps from the companies involved with validating LTS
releases, Nvidia (Raslan), Intel (John), Red Hat (Kevin implicit) and
current LTS maintainers Luca, Xueming, Kevin.

It has also has an Ack from Morten and as it is a policy change, it was
approved by the techboard at the last meeting.

thanks,
Kevin.


  reply	other threads:[~2024-06-06  9:22 UTC|newest]

Thread overview: 12+ 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
2024-05-23  9:12           ` Kevin Traynor
2024-05-23  9:15             ` Xueming Li
2024-06-06  9:22               ` Kevin Traynor [this message]
2024-06-20  3:54                 ` 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=5722f9b2-9392-4f45-9e55-1564800dd6f3@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).