From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/05/2020
Date: Thu, 28 May 2020 09:19:26 -0700 [thread overview]
Message-ID: <20200528091926.7c2b12f8@hermes.lan> (raw)
In-Reply-To: <4eac6690-f5e4-8bf5-a282-277eb2dadf44@intel.com>
On Thu, 28 May 2020 16:55:55 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Minutes 28 May 2020
> -------------------
>
> Agenda:
> * Release Dates
> * Zoom vs Skype
> * 20.05 retrospective
> * LTS
>
> Participants:
> * Arm
> * Debian/Microsoft
> * Intel
> * Mellanox
> * NXP
> * Red Hat
>
>
> Release Dates
> -------------
>
> * v20.05 is released on Tuesday 26 May
> * https://mails.dpdk.org/archives/dev/2020-May/168769.html
> * https://core.dpdk.org/download/
> * https://doc.dpdk.org/guides/rel_notes/release_20_05.html
>
> Thanks everyone who contributed.
>
> * v20.08 dates:
> * Proposal/V1: Friday, 12 June 2020
> * -rc1: Wednesday, 8 July 2020
> * -rc2: Monday, 20 July 2020
> * Release: Tuesday, 4 August 2020
>
> * Red Hat & Mellanox already sent roadmap, all contributors please send
> roadmap for the release.
>
>
> Zoom vs Skype
> -------------
>
> * Linux foundation is providing zoom accounts and should we switch the meetings
> to the Zoom, as done in the regular CI meetings?
>
> * It seems Skype is not performing well on Linux
>
> * There can be some limitations using Zoom for some companies
>
> * jitsi can be an alternative
>
> * We will give it a try, @John & @Thomas will handle the details and will
> communicate the change
>
> * In next a few meetings we will keep the Skype open to prevent confusions
>
>
Teams on Linux works quite well. Skype is being phased on legacy
next prev parent reply other threads:[~2020-05-28 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 15:55 Ferruh Yigit
2020-05-28 16:19 ` Stephen Hemminger [this message]
2020-05-28 17:54 ` Akhil Goyal
2020-06-02 11:39 ` Iremonger, Bernard
2020-06-02 14:23 ` Ferruh Yigit
2020-06-02 14:35 ` 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=20200528091926.7c2b12f8@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@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).