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 12/12/2019
Date: Thu, 12 Dec 2019 12:27:48 +0000 [thread overview]
Message-ID: <01703fa1-6a64-7ff1-85c1-a58a74f66676@intel.com> (raw)
Minutes 12 December 2019
------------------------
Agenda:
* Release Dates
* Subtrees
* OvS
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v20.02 dates:
* Proposal/V1 deadline passed, it was on Wednesday 11 December 2019
* Integration/Merge/RC1: Wednesday 15 January 2020
* Release: Friday 14 February 2020
* Reminder for 20.02 roadmaps from contributors,
Marvell & arm already sent, waiting from other contributors.
Subtrees
--------
* main
* Working on ABI breakage issue with high priority
* Consensus is not have 19.11.1 to fix it, but workaround it and live
with this workaround for ABI_20 lifetime
* David is reviewing ABI tooling patches
* next-net
* Nothing much in both backlog and the repo
* 'ionic' PMD reviewed, licensing needs to be clarified
* next-net-crypto
* eventmode to ipsec-secgw patchset will be reviewed this week
* Need to clarify CPU crypto patchset status, also Akhil will start a
discussion to clarify the techboard working group decision on matter
* For Intel crypto PMDs, the external dependent libraries are switching to
single "Intel IPSec Multi-buffer library" opensource library:
* https://github.com/intel/intel-ipsec-mb
* octeontx inline ipsec patchset is in the queue
* there is a crypto unit test update, all PMD maintainers should be aware of
these changes
* https://patches.dpdk.org/patch/63788/
* next-net-eventdev
* no update
* next-net-virtio
* Working on virtio vdpa driver, new version
* Move vdpa related code to a common folder discussion not clarified yet.
* LTS
* 17.11.10
* Some patches already backported, targeting January for release
* 18.11.6
* Another batch of patches backported
* Will send list of backport failed patches which is growing
* May have -rc mid next week
* Yunan will check if it can be validated if -rc is out next week
OvS
---
* There was OvS conference this week, videos will be available later:
http://www.openvswitch.org/support/ovscon2019/
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-12-12 12:27 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=01703fa1-6a64-7ff1-85c1-a58a74f66676@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).