From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Qian Xu <qian.q.xu@intel.com>, Yongseok Koh <yskoh@mellanox.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 20/12/2018
Date: Thu, 20 Dec 2018 18:39:53 +0000 [thread overview]
Message-ID: <e1f074a2-daaf-fc9e-c994-b915676b6c34@intel.com> (raw)
Minutes 20 December 2018
------------------------
Agenda:
* Release Dates
* RC1 deadline
* Subtrees
* OvS
* Opens
Participants:
* Debian
* Intel
* Mellanox
* RedHat
Release Dates
-------------
* v19.02 dates:
* First release candidate: December 21, 2018
* Last release candidate: January 25, 2019
* Release: February 1, 2019
* Roadmap page: http://core.dpdk.org/roadmap/#dates
RC1 deadline
------------
* First release candidate is this Friday (tomorrow)!
* It will be a hard deadline
* Power library will send a new version to fix meson build
* ipsec library, there are comments to be addressed, test team is ready
to test it in the RC1 scope
* Qian expressed she prefers a more complete RC1 rather than pushing some
features to next RC
* There is no feature planned to be pushed to RC2
* Pablo is back from holiday! (Welcome)
Subtrees
--------
* main
* Pulled from sub-trees, next-net, next-crypto, next-eventdev
* Merging patches, rapid response in mail list helps.
* next-net
* Will be ready for pull on Friday
* Pulled from next-net-intel & next-net-mlx
* next-virtio
* Will be more patches on Thursday or Friday
* next-crypto
* next-eventdev
* next-pipeline
* next-qos
* No update, we need attendance from maintainers
* Stable trees
* v16.11.9-rc1 is ready, ATT test result is good, Intel test team assessing
test plas
* Kevin will prepare an RC1 for 18.08.1 soon/today
OvS
---
* v18.11 merged to OvS master, mostly OK except a few minor fix
Opens
-----
* Coverity
* Coverity is partially back, but builds still put into queue and moves slow
* techboard has been discussed about tooling
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:[~2018-12-20 18:39 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=e1f074a2-daaf-fc9e-c994-b915676b6c34@intel.com \
--to=ferruh.yigit@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.mcnamara@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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).