From: Luca Boccassi <luca.boccassi@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: web@dpdk.org
Subject: Re: [PATCH] release 20.11.9
Date: Tue, 15 Aug 2023 18:44:08 +0100 [thread overview]
Message-ID: <CAMw=ZnR0u4TPXdAFmbV3KxS==EhUSf81zh+qKHj7+xUmPYkULw@mail.gmail.com> (raw)
In-Reply-To: <23952181.ouqheUzb2q@thomas>
On Tue, 15 Aug 2023 at 17:58, Thomas Monjalon <thomas@monjalon.net> wrote:
>
> One more release, thank you!
...and now, party time! Actually no, just more meetings.
> mardi 15 août 2023, luca.boccassi@gmail.com:
> > From: Luca Boccassi <bluca@debian.org>
> >
> > Signed-off-by: Luca Boccassi <bluca@debian.org>
>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
>
> > --- a/content/download/_index.md
> > +++ b/content/download/_index.md
> > -| [DPDK 20.11.8 (LTS)](//fast.dpdk.org/rel/dpdk-20.11.8.tar.xz) | [2023 April 27](//doc.dpdk.org/guides-20.11/rel_notes/release_20_11.html) | 12e40517446f81c79f25f6086fb2749c |
> > +| [DPDK 20.11.9 (LTS)](//fast.dpdk.org/rel/dpdk-20.11.9.tar.xz) | [2023 August 15](//doc.dpdk.org/guides-20.11/rel_notes/release_20_11.html) | 330c9c83e909097fcd24c76ccf14836c |
>
> Checked the MD5 is OK.
>
> > --- a/content/roadmap/_index.md
> > +++ b/content/roadmap/_index.md
> > -| 20.11.8 | 20.11.9 | August 2023 | December 2023 (LTS) | Luca Boccassi |
> > +| 20.11.9 | 20.11.10 | December 2023 | December 2023 (LTS) | Luca Boccassi |
>
> You are going above 3 years? I guess it will be the last 20.11 release in December.
No plan at the moment, we can discuss it in the release meeting. My
feeling is that 3 years is enough, but we can talk about it.
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2023-08-15 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 16:06 luca.boccassi
2023-08-15 16:57 ` Thomas Monjalon
2023-08-15 17:44 ` Luca Boccassi [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='CAMw=ZnR0u4TPXdAFmbV3KxS==EhUSf81zh+qKHj7+xUmPYkULw@mail.gmail.com' \
--to=luca.boccassi@gmail.com \
--cc=thomas@monjalon.net \
--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).