DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Shani Peretz <shperetz@nvidia.com>
Cc: web@dpdk.org, Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [PATCH] update 23.11.6 next version date and maintainer name
Date: Wed, 10 Dec 2025 11:55:58 +0100	[thread overview]
Message-ID: <3664102.iIbC2pHGDl@thomas> (raw)
In-Reply-To: <d8ebe752-38cb-4520-8dcd-45aee550d606@redhat.com>

10/12/2025 11:32, Kevin Traynor:
> On 10/12/2025 10:29, Shani Peretz wrote:
> > Signed-off-by: Shani Peretz <shperetz@nvidia.com>
> > ---
> >  content/roadmap/_index.md | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> > index 408b639..05fe742 100644
> > --- a/content/roadmap/_index.md
> > +++ b/content/roadmap/_index.md
> > @@ -73,5 +73,5 @@ by 3-6 weeks, depending on the test results.
> >  | 20.11.10 | -        | -                 | December 2023 (EOL) | Luca Boccassi             |
> >  | 21.11.9  | -        | -                 | December 2024 (EOL) | Kevin Traynor             |
> >  | 22.11.10 | 22.11.11 | December 2025     | December 2025 (LTS) | Luca Boccassi             |
> > -| 23.11.5  | 23.11.6  | December 2025     | December 2026 (LTS) | Xueming Li                |
> > +| 23.11.5  | 23.11.6  | January 2026      | December 2026 (LTS) | Shani Peretz              |
> >  | 24.11.3  | 24.11.4  | January 2026      | December 2027 (LTS) | Kevin Traynor             |
> 
> Thanks Shani.
> 
> Acked-by: Kevin Traynor <ktraynor@redhat.com>

You will be the maintainer of the branch 23.11, so I would change the title:
	update 23.11 maintainer and next version date

Acked-by: Thomas Monjalon <thomas@monjalon.net>



  reply	other threads:[~2025-12-10 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-10 10:29 Shani Peretz
2025-12-10 10:32 ` Kevin Traynor
2025-12-10 10:55   ` Thomas Monjalon [this message]
2025-12-10 11:02     ` 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=3664102.iIbC2pHGDl@thomas \
    --to=thomas@monjalon.net \
    --cc=ktraynor@redhat.com \
    --cc=shperetz@nvidia.com \
    --cc=web@dpdk.org \
    /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).