DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 16/04/2020
Date: Thu, 16 Apr 2020 11:06:48 +0100	[thread overview]
Message-ID: <8eca65be-5d96-7b8c-f517-9cb648972167@intel.com> (raw)

Minutes 16 April 2020
---------------------

Agenda:
* Release Dates
* Subtrees
* OvS

Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat


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

* v20.05 dates:
  * Integration/Merge/RC1 pushed to	*Thursday 23 April 2020*
  * Release:				Wednesday 20 May 2020

  * Marvell, Arm, Mellanox & Broadcom already sent roadmap for 20.05, all
    vendors please share the roadmap for the release.


Subtrees
--------

* main
    * There are still lots of patches, a lot of reviews are missing
    * Sub-trees will be pulled next week Monday/Tuesday
      * Sub-trees should be ready by EOD Friday or Saturday
    * Thomas did review on graph library, planning to get it as it is
    * Trace library will be merged for -rc1, the review was missing but at least
      feedback requested
    * Some library features may go in for -rc2 due to big backlog
    * If the work is not finished, planning to block related patches
      * Example: ABI breaks for false positive, don't get patches that
                 breaks ABI before fixing the ABI check tools.

* next-net
  * Less than 50 patches in the backlog
  * Some ethdev patches are not merged yet, close but not ready for -rc1
  * mlx set that break the ABI not clarified yet, it may be dropped from tree

* next-crypto
  * ~50 patches in backlog, reviewed most of them, will apply today
  * ipsec patch depends on hash change which is for main repo
    * Thomas will look to it with priority
  * ABI related crypto patch will be reviewed today
  * There is a reported build error from Raslan

* next-eventdev
  * No more patches for -rc1, already pulled to main

* next-virtio
  * Lots of reviews done last and this week, still have bunch of patches
  * Some reviewed already and can be merged quickly
  * Ones waiting for new version can go into next -rc
  * There is a performance optimization for Arm patch waiting for review
    * one way barrier for split vring idx

* next-net-intel
  * Waiting for some major patchsets related to iavf
  * They may not be ready for tomorrow

* next-net-mlx
  * There are some big patchsets waiting, they are not blocking the -rc1
  * flow aging patches waiting to be merged in next-net

* next-net-mrvl
  * All patches merged for -rc1

* next-net-brcm
  * There is a big patch merged recently, will pull it to next-net today

* LTS

  * 18.11.7 released
    * http://inbox.dpdk.org/dev/20200415173701.19706-1-ktraynor@redhat.com/


OvS
---

* There was another meeting last week, ping Kevin for details.



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:[~2020-04-16 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 10:06 Ferruh Yigit [this message]
2020-04-16 10:49 ` Thomas Monjalon
2020-04-16 11:21   ` 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=8eca65be-5d96-7b8c-f517-9cb648972167@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).