From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 5/03/2020
Date: Thu, 5 Mar 2020 13:22:59 +0000 [thread overview]
Message-ID: <bc8eed45-65c8-e26f-9a79-d31508fb4a03@intel.com> (raw)
Minutes 5 March 2020
--------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Opens
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* Red Hat
Release Dates
-------------
* v20.05 dates:
* Proposal/V1: Wednesday 18 March 2020
* Integration/Merge/RC1: Friday 17 April 2020
* Release: Wednesday 20 May 2020
* Marvell already sent roadmap for 20.05, all vendors please share the
roadmap for the release.
Subtrees
--------
* main
* There are some work in eal
* Working on CI (travis)
* Will be good to have __rte_intenal patches
* GCC 10 needs to be fixed
* Will ask in Intel for the resource for it
* It would be good to do early merges from sub-trees
* One will be done early next week
* next-net
* Some patches are merged
* Need to resolve ethdev RFCs as soon as possible
* next-crypto
* Anoob reminded ipsec-secgw eventmode patches to be merged early in this
release cycle
* next-eventdev
* No patches as of now
* next-virtio
* Nothing big as of now
* Xiaolong is additional maintainer for vhost/virtio now
* Currently Maxime is the only maintainer for virtio tree, good to have backup
* next-net-intel
* Not too many patches in backlog, some already merged
* Gavin mentioned there will be some patches from Arm
* Arm will send Intel & Mellanox NIC patches
* Kevin commented it may be good to get more help from Intel NIC maintainers
to Xiaolong taking into account his extended virtio/vhost tasks
* LTS
* 17.11.10 released
* https://mails.dpdk.org/archives/dev/2020-February/158735.html
* It has been EOL, thanks everyone worked on it
* 18.11.7
* Majority of the backports done
* -rc1 expected end of next week, 13 March
* Release planned for April, depending validation
* 19.11.1-rc1 released, please test and report results
* https://mails.dpdk.org/archives/dev/2020-March/158923.html
* Release planned for end of March
OvS
---
* Intel is planning to propose using vhost PMD in OvS
* Also there may be some updates in DPDK vhost sample apps,
since they look outdated.
* OVS-DPDK meeting was yesterday, thanks Kevin for notes and recording:
* https://mails.dpdk.org/archives/dev/2020-March/159150.html
* Interested parties invited for follow up discussions
Opens
-----
* We should make NIC feature matrix more readable, Thomas has an idea
* https://doc.dpdk.org/guides/nics/overview.html
* Thomas suggested defining minimum set of required feature for the NICs,
we can discuss this more in the mail list
DPDK Release Status Meetings
============================
The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.
The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
reply other threads:[~2020-03-05 13:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bc8eed45-65c8-e26f-9a79-d31508fb4a03@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).