From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 4/10/2018
Date: Fri, 5 Oct 2018 19:09:47 +0100 [thread overview]
Message-ID: <72ac5a3b-42f0-7c7d-a0bb-0e50c5cacc0d@intel.com> (raw)
Minutes 4 October 2018
----------------------
Agenda:
* Dates
* Subtrees
* Bugzilla
Participants:
* Intel
* RedHat
* Mellanox
Release Dates
-------------
* RC1 date *pushed a week*, it is now *12th October 2018*
* Delay is because of existing patch backlog.
Subtrees
--------
* main
* Still lots of patches/reviews to be done
* There is Anatoly's large patchset (external memory) to be merged
* Hotplug must be done in this release, Thomas will send more patches
* next-net
* 2 new PMDs merged Marvell MVNETA & NXP ENETC
* Aquantia Atlantic PMD may not go in this release, doesn't look ready
* AF_XDP PMD still an RFC, won't be in this release
* ~50 patches to merge, mainly rte_flow ones
* most rte_flow ones will be merged this week if there is no objection
* vendor trees
* next-net-intel: small set of fixes, can go in after rc1
* next-net-mlx: waiting it to be ready
* There is a process_private data field patch, it may go in since there will
be API break on ethdev already.
Thomas will send more patches to add Port Representor ID field.
* next-crypto
* Already pulled
* next-virtio
* 2 main features to get ready
* packed virtqueues & postcopy live-migration
* next-eventdev
* Already pulled
* Probably won't be any more major changes
* Merge caused an ICC build error, fix patch is out
* next-pipeline
* next-qos
* Pull request sent, there is a few more patches for the tree
Bugzilla
--------
* Ajit managing defects, assigning them
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 me and email and I will send you the invite.
reply other threads:[~2018-10-05 18:09 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=72ac5a3b-42f0-7c7d-a0bb-0e50c5cacc0d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
/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).