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 28/3/2019
Date: Thu, 28 Mar 2019 12:03:32 +0000	[thread overview]
Message-ID: <8a5c4ea4-11fb-8b9f-830e-c9e7ff4effec@intel.com> (raw)
Message-ID: <20190328120332.Lq4gEOmgIsrCKUm0OhE1Bq-mxtdGB6fkGcVmEyn9Od8@z> (raw)

Minutes 28 March 2019
---------------------

Agenda:
* Release Dates
* Subtrees
* Coverity
* Opens


Participants:
* Arm
* Intel
* Marvell
* Mellanox
* NXP
* RedHat


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

* v19.05 dates, rc1 date pushed to Wednesday:
  * RC1: *Wednesday, 3 April*
  * Release: Friday, 10 May

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

  * schedule update patch:
    https://mails.dpdk.org/archives/web/2019-March/001055.html

* v19.11 dates should be discussed soon


Subtrees
--------

* main
  * More patches to merge
  * Thomas is looking Arm locking patches

* next-net
  * Around 60 patches waiting for review
  * New pmds not merged yet: af_xdp, memif, ifpga ipn3ke, netcope nfb
    * af_xdp updates some other libraries, may go in rc2
    * memif may not make this release

* next-virtio
  * Patches has been merged, tree pulled

* next-crypto
  * ipsec updates mbuf, needs to be addressed
  * ipsec-secgw can be slip to rc2

* next-eventdev
  * no update

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

* Stable trees
  * 18.08.1-rc3 is waiting for more test
    * 18.08.1 release planned for next Monday
  * 18.11-1-rc2 is out, waiting to be tested
    * Intel & Mellanox test result look good
    * 18.11.1 release planned on 8 April
  * 19.02
    * Short term stable releases discussed on techboard,
      more detail will be on techboard meeting minutes
    * Will be dropped unless there is volunteer
  * 19.11
    * Luca may be tree maintainer


Coverity
--------

* Coverity is back on, John run a new scan with latest code:
  https://scan.coverity.com/projects/dpdk-data-plane-development-kit

* John shared lgtm.com results to the mail list:
  * https://mails.dpdk.org/archives/dev/2019-March/127986.html
  * lgtm dpdk project link:
    https://lgtm.com/projects/g/DPDK/dpdk/alerts/?mode=list


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 12:03 Ferruh Yigit [this message]
2019-03-28 12:03 ` Ferruh Yigit
2019-03-28 12:48 ` David Marchand
2019-03-28 12:48   ` David Marchand
2019-04-01 15:47   ` Mcnamara, John
2019-04-01 15:47     ` Mcnamara, John
2019-04-01 19:10     ` David Marchand
2019-04-01 19:10       ` David Marchand
2019-04-02  9:35       ` Bruce Richardson
2019-04-02  9:35         ` Bruce Richardson

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=8a5c4ea4-11fb-8b9f-830e-c9e7ff4effec@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).