From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org, bluca@debian.org, xuemingl@nvidia.com,
david.marchand@redhat.com
Subject: Re: [PATCH] release 24.11.3
Date: Mon, 18 Aug 2025 18:13:16 +0100 [thread overview]
Message-ID: <f8ed6035-15d9-4064-80a4-efb2f2f85dcc@redhat.com> (raw)
In-Reply-To: <6161378.alqRGMn8q6@thomas>
On 18/08/2025 17:04, Thomas Monjalon wrote:
> 18/08/2025 18:00, Kevin Traynor:
>> - 24.11.2
>> + 24.11.3
>> -| [DPDK 24.11.2 (LTS)](//fast.dpdk.org/rel/dpdk-24.11.2.tar.xz) | [2025 April 23](//doc.dpdk.org/guides-24.11/rel_notes/release_24_11.html) | dae5ac259126e6912afa5051f6665851 |
>> +| [DPDK 24.11.3 (LTS)](//fast.dpdk.org/rel/dpdk-24.11.3.tar.xz) | [2025 August 18](//doc.dpdk.org/guides-24.11/rel_notes/release_24_11.html) | 5e2cd8cbbe3097697e6800b3480dcc95 |
>
> Looks fine, thanks.
>
>> -| 24.11.2 | 24.11.3 | August 2025 | December 2027 (LTS) | Kevin Traynor |
>> +| 24.11.3 | 24.11.4 | January 2026 | December 2027 (LTS) | Kevin Traynor |
>
> Why not 24.11.4 in December?
>
>
It would be an aim, but last year validation teams were unable to commit
to test LTS releases before we had CVE releases on Dec 17th. In the end
they found some extra cycles to do it.
It was 3 weeks turnaround on testing this latest release, so we can
creep into holiday season and people OoO too.
So it could be either month and my thinking is I don't want anyone to
plan for it getting it in December and be left waiting. I'm not strongly
opposed to saying December, just it might be late.
next prev parent reply other threads:[~2025-08-18 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 16:00 Kevin Traynor
2025-08-18 16:04 ` Thomas Monjalon
2025-08-18 17:13 ` Kevin Traynor [this message]
2025-08-18 17:17 ` 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=f8ed6035-15d9-4064-80a4-efb2f2f85dcc@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
--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).