From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 1/8/2019
Date: Fri, 2 Aug 2019 11:35:12 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE24BCA95CA@IRSMSX103.ger.corp.intel.com> (raw)
Minutes 1 August 2019
--------------------
Agenda:
* Release Dates
* RC3 Status
* Subtrees
* OvS
* Opens
Participants:
* Cavium/Marvell
* Debian/Microsoft
* Intel
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v19.08 dates:
* RC2 is released on Tuesday 23 July
* https://mails.dpdk.org/archives/announce/2019-July/000270.html
* RC3 is released on Wednesday 31 July
* https://mails.dpdk.org/archives/announce/2019-July/000272.html
* RC4 Tuesday 6 August
* Release Saturday 10 August
* v19.11 dates:
* Proposal/V1 Friday 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
RC3 Status
----------
* No test results available yet. Please submit test results to the list.
Subtrees
--------
* Next-Net
* No patches after RC3.
* Next-virtio
* Compilation issue for NXP.
* Next-Crypto
* No patches after RC3.
* Next-Eventdev
* No patches after RC3.
* Master
* Patches for network drivers.
* Power PC issues due to IOVA changes.
* Some patches for documentation, SPDX, etc.
* Stable trees
* 17.11 backported some patches for 17.11.7, no rc yet
* A request sent to authors to backport some patches
OvS
---
* Feature freeze done for 2.12, will take ~4 weeks, release ~22 August
* Some features vhost optimizations, af_xdp support, onv changes started
Opens
-----
* A new coverity scan done by John, there are new defects reported.
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-08-02 11:35 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=B27915DBBA3421428155699D51E4CFE24BCA95CA@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).