From: Luca Boccassi <bluca@debian.org>
To: dev <dev@dpdk.org>
Cc: Xueming Li <xuemingl@nvidia.com>,
Kevin Traynor <ktraynor@redhat.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Subject: Next year of LTSes
Date: Thu, 9 Nov 2023 10:30:03 +0000 [thread overview]
Message-ID: <CAMw=ZnQKjTop=Adt8GSSxZH2s7PnPzgB92eZuzDLJmsKh0OboQ@mail.gmail.com> (raw)
Hi,
We should start thinking about the next year of LTSes and how to organize.
20.11 will be EOL after the next upcoming release being prepared now,
as it's now 3 years old. So long, and thanks for all the fixes.
Currently Kevin is taking care of 21.11 and Xueming of 22.11.
Xueming, what do you think about, from next year (ie, after the
current set is done) me taking over 22.11, and you switching to 23.11?
The reason is that Debian uses "even" releases due to release cadence,
so just like I had vested interest for 20.11 for Debian 11, Debian 12
uses 22.11.
Kind regards,
Luca Boccassi
next reply other threads:[~2023-11-09 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 10:30 Luca Boccassi [this message]
2023-12-07 9:50 ` Luca Boccassi
2023-12-08 8:58 ` Xueming(Steven) Li
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='CAMw=ZnQKjTop=Adt8GSSxZH2s7PnPzgB92eZuzDLJmsKh0OboQ@mail.gmail.com' \
--to=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--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).