DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 2/07/2020
Date: Thu, 2 Jul 2020 15:58:05 +0100	[thread overview]
Message-ID: <4292b290-6b8f-9c7f-3e1f-8df4bf28be17@intel.com> (raw)

Minutes 2 July 2020
-------------------

Agenda:
* Release Dates
* Highlights
* Subtrees
* LTS


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


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

* v20.08 dates:
  * -rc1:           Wednesday, 8 July   2020
  * -rc2:           Monday,   20 July   2020
  * Release:        Tuesday,   4 August 2020

* v20.11 proposal dates, please comment:
  * Proposal/V1:    Wednesday, 2 September 2020
  * -rc1:           Wednesday, 30 September 2020
  * -rc2:           Friday, 16 October 2020
  * Release:        Friday, 6 November 2020


Highlights
----------

* We are close to -rc1 but still lots of patches in backlog waiting for review
  *Please help on code reviews*, missing code reviews may lead some features
  missing the release.
  Please check "call for reviews" email for the list of patches to review:
  https://mails.dpdk.org/archives/announce/2020-June/000329.html

* Please subscribe to patchwork to be able to update status of your patches,
  not updating them adding overhead to the maintainers.
  * We are observing an issue in Intel, that not receiving patchwork
    registration and lost password emails.
    * If there is anyone else outside Intel having the same problem please reach
      out to help analyzing the problem.
    * Within Intel please reach to Ferruh if there are patches their status
      needs update in patchwork and you don't have the access.


Subtrees
--------

* main
  * Started to merge ring and vfio patches
  * Would like to close following
    * non-EAL threads as lcore from David
    * rte_log registration usage improvement from Jerin
    * if-proxy
      * Stephen reviewed the patch
    * regex
      * Waiting for PMD implementations. How many PMD required for merge?
      * A HW and two SW PMDs were planned
  * Worrying that ethdev doesn't have enough review
    * Jerin did review on some rte flow ones

* next-net
  * Pulled from vendor sub-trees
  * Some big base update patches from Intel and bnxt merged
  * Need to get ethdev patches before -rc1, requires more review

* next-crypto
  * Reviewed half of the backlog
  * Will be good for -rc1
  * cryptodev patches has been reviewed

* next-eventdev
  * Almost ready for -rc1
  * Intel DLB PMD new version still has ABI breakage
    * Postponed to next release because of the ABI
    * No controversial issues otherwise

* next-virtio
  * Maxime did a pull request for majority of the patches
  * Maxime sent a status for remaining ones
    * 2 patches for async datapath, looks good
    * 2 patches for vhost-user protocol features
      * Has a dependency to quemu
      * Adrian from Red Hat will takeover the patches
    * Performance optimization (loops vectorization)
      * Waiting for new version
      * Not critical for this release, may be postponed if needed
  * Chenbo is managing the virtio patches during Maxime's absence

* next-net-intel
  * Qi is actively merging patches
  * Some base code updates already merged
  * DCF datapath merged

* next-net-mlx
  * Some patches already merged
  * Expecting more but not many

* next-net-mrvl
  * A few patches merged
  * Two more patches for -rc1
  * change requested for qede patches, can merge when they are ready


LTS
---

* v18.11.9-rc2 is out, please test
  * https://mails.dpdk.org/archives/dev/2020-June/171690.html
  * OvS testing reported an issue
    * A workaround can exist for it
  * Nvidia reported an error
    * Which is not regression for 18.11.9 release
  * The release is planned on end of this week or early next week



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 every Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK

If you wish to attend just send an email to
"John McNamara <john.mcnamara@intel.com>" for the invite.

                 reply	other threads:[~2020-07-02 14:58 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=4292b290-6b8f-9c7f-3e1f-8df4bf28be17@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).