From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@amd.com>
Cc: "web@dpdk.org" <web@dpdk.org>,
David Marchand <david.marchand@redhat.com>
Subject: RE: [PATCH] update 22.11.0 schedule
Date: Thu, 3 Nov 2022 20:07:03 +0000 [thread overview]
Message-ID: <DM6PR11MB3227EDC8B480A87E1B793CB5FC389@DM6PR11MB3227.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1996030.0S5aU1g85B@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, November 3, 2022 4:11 PM
> To: Ferruh Yigit <ferruh.yigit@amd.com>
> Cc: web@dpdk.org; David Marchand <david.marchand@redhat.com>; Mcnamara,
> John <john.mcnamara@intel.com>
> Subject: Re: [PATCH] update 22.11.0 schedule
>
> 03/11/2022 16:56, Ferruh Yigit:
> > As discussed in the maintainers meeting, updated -rc3 date, delayed
> > around 10 days.
> >
> > Updated -rc1 & -rc2 dates to reflect actual release dates:
> > -rc1: https://inbox.dpdk.org/announce/13255994.nUPlyArG6x@thomas/T/#u
> > -rc2: https://inbox.dpdk.org/announce/6919521.aoefvbuG5b@thomas/T/#u
> >
> > Signed-off-by: Ferruh Yigit <ferruh.yigit@amd.com>
>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
>
> > +- API freeze (-rc1): 11 October 2022
> > +- PMD features freeze (-rc2): 1 November 2022
> > +- Builtin applications features freeze (-rc3): 10 November 2022
> > - Release: 16 November 2022
>
> Note that we'll need to postpone the release date as 16 November is not
> realistic anymore.
>
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2022-11-03 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 15:56 Ferruh Yigit
2022-11-03 16:10 ` Thomas Monjalon
2022-11-03 20:07 ` Mcnamara, John [this message]
2022-11-09 17:39 ` Thomas Monjalon
2022-11-10 10:30 Thomas Monjalon
2022-11-10 10:37 ` Devlin, Michelle
2022-11-10 14:26 ` Ferruh Yigit
2022-11-11 23:44 ` Thomas Monjalon
2022-11-11 11:15 ` Mcnamara, John
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=DM6PR11MB3227EDC8B480A87E1B793CB5FC389@DM6PR11MB3227.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@amd.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).