DPDK website maintenance
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>
Cc: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
	"web@dpdk.org" <web@dpdk.org>
Subject: RE: [PATCH] update roadmap for LTS 20.11 and 22.11
Date: Thu, 12 Jan 2023 13:03:33 +0000	[thread overview]
Message-ID: <DM4PR12MB537303E09EDB4BFE44B38A63A1FD9@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAATJJ0+-LEQp6fz3b9gckkNF+O2hR849pbZ+A7rCGryocgTUYQ@mail.gmail.com>



> -----Original Message-----
> From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> Sent: Thursday, January 12, 2023 19:07
> To: Kevin Traynor <ktraynor@redhat.com>
> Cc: luca.boccassi@gmail.com; web@dpdk.org; Xueming(Steven) Li
> <xuemingl@nvidia.com>
> Subject: Re: [PATCH] update roadmap for LTS 20.11 and 22.11
> 
> On Thu, Jan 12, 2023 at 11:18 AM Kevin Traynor <ktraynor@redhat.com> wrote:
> >
> > On 12/01/2023 10:07, luca.boccassi@gmail.com wrote:
> > > From: Luca Boccassi <bluca@debian.org>
> > >
> > > 20.11 will continue for another year maintained by me, and
> > > 22.11 will be maintained by Xueming.
> > >
> > > Signed-off-by: Luca Boccassi <bluca@debian.org>
> > > ---
> > >   content/roadmap/_index.md | 4 ++--
> > >   1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
> > > index bfdab34..57ed8bf 100644
> > > --- a/content/roadmap/_index.md
> > > +++ b/content/roadmap/_index.md
> > > @@ -135,6 +135,6 @@ by 3-6 weeks, depending on the test results.
> > >   |----------|----------|-------------------|---------------------|-------------------------
> --|
> > >   | 18.11.11 | -        | -                 | December 2020 (EOL) | -                         |
> > >   | 19.11.14 | -        | -                 | December 2022 (EOL) | Christian Ehrhardt
> |
> > > -| 20.11.7  | -        | -                 | December 2022 (EOL) | -                         |
> > > +| 20.11.7  | 20.11.8  | April 2023        | December 2023 (LTS) | Luca Boccassi
> |
> > >   | 21.11.3  | 21.11.4  | April 2023        | November 2023 (LTS) | Kevin Traynor
> |
> > > -| 22.11.1  | 22.11.2  | April 2023        | November 2024 (LTS) |
> |
> > > +| 22.11.1  | 22.11.2  | April 2023        | November 2024 (LTS) | Xueming Li
> |
> >
> > Thanks Luca and Xueming.
> 
> Indeed, thank you both!
> Acked-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> 
> > Acked-by: Kevin Traynor <ktraynor@redhat.com>
> >
Acked-by: Xueming Li <xuemingl@nvidia.com>

> 
> 
> --
> Christian Ehrhardt
> Senior Staff Engineer, Ubuntu Server
> Canonical Ltd

      reply	other threads:[~2023-01-12 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 10:07 luca.boccassi
2023-01-12 10:18 ` Kevin Traynor
2023-01-12 11:07   ` Christian Ehrhardt
2023-01-12 13:03     ` Xueming(Steven) Li [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=DM4PR12MB537303E09EDB4BFE44B38A63A1FD9@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=christian.ehrhardt@canonical.com \
    --cc=ktraynor@redhat.com \
    --cc=luca.boccassi@gmail.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).