DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 8/10/2020
Date: Thu, 8 Oct 2020 15:47:43 +0100	[thread overview]
Message-ID: <ed8ceb1d-d8ab-b667-8ecb-3e77170e7774@intel.com> (raw)
In-Reply-To: <5f9981a8-647a-af70-fcb2-40edff3cec0d@intel.com>

On 10/8/2020 1:54 PM, Ferruh Yigit wrote:
> Meeting minutes of 8 October 2020
> ---------------------------------
> 
> Agenda:
> * Release Dates
> * Subtrees
> * OvS
> 
> Participants:
> * Broadcom
> * Debian/Microsoft
> * Intel
> * Marvell
> * Nvidia
> * NXP
> * Red Hat
> 
> 
> Release Dates
> -------------
> 
> * v20.11 dates
>    * -rc1:           Friday, 16 October 2020
>    * -rc2 pushed to  *Friday, 23 October 2020*
>    * Release:        Friday, 13 November 2020
> 

The -rc2 date above is wrong, thanks Asaf for catching it,
correct one is as below:

* -rc2 pushed to  *Friday, 30 October 2020*

  reply	other threads:[~2020-10-08 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 12:54 Ferruh Yigit
2020-10-08 14:47 ` Ferruh Yigit [this message]
2020-10-09 16:56 ` Stephen Hemminger
2020-10-09 17:30   ` 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=ed8ceb1d-d8ab-b667-8ecb-3e77170e7774@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).