From: Asaf Penso <asafp@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Shani Peretz <shperetz@nvidia.com>, Luca Boccassi <bluca@debian.org>
Subject: RE: New LTS maintainer?
Date: Wed, 10 Dec 2025 12:28:46 +0000 [thread overview]
Message-ID: <MN0PR12MB60533543EC745C2CA1ED6F62CDA0A@MN0PR12MB6053.namprd12.prod.outlook.com> (raw)
In-Reply-To: <5a74618a-0f23-4ddb-92a3-610054689b6c@redhat.com>
Good luck Shani!
Regards,
Asaf Penso
>-----Original Message-----
>From: Kevin Traynor <ktraynor@redhat.com>
>Sent: Wednesday, 10 December 2025 12:42
>To: dev@dpdk.org
>Cc: Shani Peretz <shperetz@nvidia.com>; Luca Boccassi <bluca@debian.org>
>Subject: Re: New LTS maintainer?
>
>On 29/10/2025 16:30, Kevin Traynor wrote:
>> Hi All,
>>
>> tl;dr we are looking for a new LTS maintainer.
>>
>
>A big thank you to Shani Peretz of Nvidia who volunteered and was
>unanimously approved as the new LTS maintainer for 23.11 at the 12th
>November techboard meeting.
>
>> We have 3 maintained LTS releases and a maintainer responsible for
>> each one as listed at https://core.dpdk.org/roadmap/#stable .
>>
>> Xueming has done a great job maintaining 23.11 LTS up to now but is
>> stepping down as maintainer due to changing work priorities, so we are
>> looking for a new LTS maintainer to take over 23.11 for it's final
>> year and a bit.
>>
>> The main items the role involves:
>> - Getting a list of fixes from main branch that should be backported
>> to the LTS branch around time of a new DPDK release
>> - Backporting the fixes to the LTS branch
>> - Resolving any trivial conflicts (and complex ones if you want)
>> - Notifying authors of fixes that could not be backported and require
>> their assistance
>> - Notifying authors of fixes that are queued to merge
>> - Ensuring that CI's are kept green
>> - Creating release candidates for the validation teams
>> - Working with validation teams and authors to get a resolution for
>> any issues that are found during testing
>> - Writing up release notes etc. and releasing
>>
>> We have many scripts and tricks to help semi-automate the steps above.
>>
>> Luca and I will continue as LTS maintainers so we'll be available to
>> help someone ramp up and only a ping away for any issues.
>>
>> If anyone is interested please send me a private email reply by Nov
>> 7th and we'll propose candidates to the techboard.
>>
>> thanks,
>> Kevin and Luca.
prev parent reply other threads:[~2025-12-10 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 16:30 Kevin Traynor
2025-12-10 10:42 ` Kevin Traynor
2025-12-10 12:28 ` Asaf Penso [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=MN0PR12MB60533543EC745C2CA1ED6F62CDA0A@MN0PR12MB6053.namprd12.prod.outlook.com \
--to=asafp@nvidia.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=shperetz@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).