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 7/11/2019
Date: Thu, 7 Nov 2019 15:01:12 +0000 [thread overview]
Message-ID: <6f411b3e-4334-6240-0e30-1d30512f0731@intel.com> (raw)
Minutes 7 November 2019
-----------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Conferences
* Opens
Participants:
* Debian/Microsoft
* Intel
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v19.11 dates:
* RC1 is released on Sunday 27 October
* https://mails.dpdk.org/archives/announce/2019-October/000284.html
* RC2 Friday 8 November
* RC3 Friday 15 November
* Release Friday 22 November
* Proposed dates for 20.02 :
* Proposal/V1: Friday 6 December 2019
* Integration/Merge/RC1: Wednesday 15 January 2020
* Release: Friday 14 February 2020
Subtrees
--------
* main
* ABI/API patches, and tooling reviews are going on, more review welcome
* ABI policy:
v8: https://patches.dpdk.org/project/dpdk/list/?series=7255&state=*
* tooling
v6: https://patches.dpdk.org/project/dpdk/list/?series=7299&state=*
https://patches.dpdk.org/project/dpdk/list/?series=7004
* WFE under review
v12: https://patches.dpdk.org/project/dpdk/list/?series=7224&state=*
* LTO series in the queue
v6: https://patches.dpdk.org/project/dpdk/list/?series=7128&state=*
* vfio fixes may be pushed today
* new arm target patch under review
* mempool patch applied, KNI iova=va patch can go in after review
* Windows series can go in rc3
* next-net
* There are more ethdev patches that will be included in rc2
* configure SR-IOV VF from host patch will be deferred to next release
* Will merge as much for rc2 but remaining will be deferred to next rc
* Will make next-net ready for rc2 on Friday morning
* next-net-crypto
* Almost ready for rc2
* Future of the arm based crypto is not clear
* ipsec-secgw, set default to IPsec library mode deferred to next release
* Compression, waiting for new version
* A work-group established in techboard to decide on CPU crypto decisions
* next-net-eventdev
* pull request sent, planned to pull today
* next-net-virtio
* Sent pull request, ready for rc2
* next-net-intel
* ipn3ke PMD waiting for a new version
* LTS
* v18.11.3 is released
https://mails.dpdk.org/archives/announce/2019-October/000283.html
* Next week Kevin will start backporting patches for next release
OvS
---
* vhost patch to enable large buffer support merged, this will help enabling TSO
in OvS.
Conferences
-----------
* DPDK Summit North America, Mountain View CA, November 12-13
https://www.dpdk.org/event/dpdk-summit-na-mountain-view/
Opens
-----
* Governing board triggered some questions related DPDK community lab,
we can have more discussion soon related to utilizing the lab better
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:[~2019-11-07 15:01 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=6f411b3e-4334-6240-0e30-1d30512f0731@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).