From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>,
"Stokes, Ian" <ian.stokes@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 21/2/2019
Date: Thu, 21 Feb 2019 16:09:00 +0000 [thread overview]
Message-ID: <83259c98-9d32-02d8-fe09-d67839658eca@intel.com> (raw)
Minutes 21 February 2019
------------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Opens
Participants:
* Arm
* Debian
* Intel
* Mellanox
* NXP
* RedHat
Release Dates
-------------
* v19.05 dates, no change:
* Proposal Deadline: Friday, 1 March
* RC1: Friday, 29 March
* Release: Friday, 10 May
* Schedule web page updated accordingly:
http://core.dpdk.org/roadmap/#dates
* Contributors please provide 19.05 roadmap whenever available
* Mellanox, Arm & Intel sent, RedHat? NXP? Marvel? others?
* v19.08 proposal, please comment:
* Proposal/V1 Friday 07 June 2019
* Integration/Merge/RC1 Friday 05 July 2019
* Release Thurs 01 August 2019
Subtrees
--------
* main
* Planning a merge from sub-trees on the end of the week
* There is a concern around windows work, it needs:
* early, small, incremental patches for better engage with community
* next-net
* Nothing critical/open
* next-virtio
* Can get some patches this week
* next-crypto
* Akhil will be able to work on it this week
* Need support on BBDev and Compressdev work
* next-eventdev
* next-pipeline
* next-qos
* No update, we need attendance from maintainers
* Stable trees
* 17.11.5 merged one released
* 16.11.9 is the last release of 16.11, will wait for more test
* There is a concern on missing response from developers on backport request
for a stable/LTS tree.
* For example the list of skipped patches because of developer support is at
the end of the 17.11.5 release email:
http://mails.dpdk.org/archives/announce/2019-February/000244.html
OvS
---
* 2.11 release should be this week
Opens
-----
* Akhil is looking for co-maintainer for crypto sub-tree,
any volunteer please contact to Akhil or Thomas.
* Coverity is partially back, but new analyses aren't running
* Looking for suggestions from the community for a better or more stable
solutions
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.
next reply other threads:[~2019-02-21 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 16:09 Ferruh Yigit [this message]
2019-02-21 16:19 ` Thomas Monjalon
2019-02-21 17:43 ` Luca Boccassi
2019-02-21 18:16 ` Thomas Monjalon
2019-03-06 15:27 ` Luca Boccassi
2019-03-06 15:45 ` Richardson, Bruce
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=83259c98-9d32-02d8-fe09-d67839658eca@intel.com \
--to=ferruh.yigit@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@intel.com \
--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).