DPDK patches and discussions
 help / color / mirror / Atom feed
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/3/2019
Date: Thu, 21 Mar 2019 12:38:48 +0000	[thread overview]
Message-ID: <57fbec5c-2f49-0809-be4f-e821720a3b03@intel.com> (raw)
Message-ID: <20190321123848.mIQXTUfCCIMpXraNfsEYKHSzV8Xs7TBkJqJrnd7-6lE@z> (raw)

Minutes 21 March 2019
---------------------

Agenda:
* Release Dates
* Subtrees
* OvS
* Coverity
* Opens


Participants:
* Arm
* Debian
* Intel
* Mellanox
* RedHat


Release Dates
-------------

* v19.05 dates, no change:
  * RC1: Friday, 29 March
  * Release: Friday, 10 May

  * Schedule web page updated accordingly:
    http://core.dpdk.org/roadmap/#dates

* v19.08 proposal:
  * Proposal/V1               Monday 03 June   2019  
  * Integration/Merge/RC1     Monday 01 July   2019  
  * Release                   Thurs  01 August 2019

  * Received a roadmap item from Rami for Huawei
    * Great to see more engagement for upstreaming


Subtrees
--------

* main
  * More patches to merge, nothing major at this point
  * Features of the release to pay attention:
    * Arm locking patches
      * Need more review
      * Intel side is doing some benchmarks, Arm observes performance increase
    * Windows patches, requires three things:
      * Need public roadmap
      * Upstream effort, which is already happening
      * Push changes into dpdk-draft-windows repo
    * More eal patches to review/merge
  * There will be regular merge from sub-trees at end of the week

* next-net
  * nothing critical/urgent at this point
  * New pmds not merged yet: af_xdp, memif, ifpga ipn3ke, netcope nfb
    * All are waiting for new version,
    * Should be able to merge them next week to be on time for RC1
    * memif still has eal dependency
  * Some stats, ethdev read_clock API, etc.. waiting, nothing major

* next-virtio
  * Most of the patches has been merged, tree pulled
  * Nothing major waiting for RC1

* next-crypto
  * Akhil applied some patches this week
  * Need to clarify if the sub-tree will be ready for merge this week

* next-eventdev
  * Pulled previous week

* next-pipeline
* next-qos
  * No update, we need attendance from maintainers

* Stable trees
  * 16.11.9 released. This was the last 16.11 LTS release
    * Thanks to Luca and all supported for the work
  * 17.11.6 will be next release with 19.02 changes
  * 18.08.1-rc3 is waiting for more test
    * Intel test results received
      * One issue reported, analyzed as not introduced in this release
    * 18.08.1 release planned for next week
  * 18.11-1-rc1 is out, waiting to be tested
    * -rc2 will be created with a few post 19.02 critical patches
    * -rc2 planned for next a few days
    * 18.11.1 release planned on 8 April
  * 19.02
    * There is no maintainer right now
    * The 19.02 short term stable tree may be dropped
    * Will be discussed in next techboard meeting, on next Wednesday
    * Decision will be announced


OvS (received offline)
----------------------

* Roni Bar Yani did a readout on hardware offload in OVS-DPDK using
  rte_flow. Link to slides and recording here
  * https://mail.openvswitch.org/pipermail/ovs-dev/2019-March/357413.html


Coverity
--------

* Coverity is back on, John run a new scan with latest code:
  * https://scan.coverity.com/projects/dpdk-data-plane-development-kit?tab=overview
    * 293 Outstanding defects!

* There were other tools suggested in mail list:
  * https://mails.dpdk.org/archives/dev/2019-February/125006.html
  * sonarcloud.io
    * https://sonarcloud.io/dashboard?id=bluca_dpdk
      * 215 Bugs
  * lgtm.com
    * https://lgtm.com/projects/g/DPDK/dpdk/alerts/?mode=list
      * 211 Alerts


Opens
-----

* Akhil is looking for co-maintainer for crypto sub-tree,


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-03-21 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 12:38 Ferruh Yigit [this message]
2019-03-21 12:38 ` Ferruh Yigit

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=57fbec5c-2f49-0809-be4f-e821720a3b03@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).