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 9/04/2020
Date: Thu, 9 Apr 2020 13:42:18 +0100	[thread overview]
Message-ID: <0e082fc8-c60c-f62b-ef22-4b453e193567@intel.com> (raw)

Minutes 9 April 2020
--------------------

Agenda:
* Release Dates
* Highlights
* Subtrees

Participants:
* Arm
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat


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

* v20.05 dates:
  * Integration/Merge/RC1:	Friday 17 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.


Highlights
----------

* CI failures (ones reported in patchwork)
  **We will be more strict and failing patches will be blocked**


Subtrees
--------

* main
    * crypto tree will be pulled today
    * There is lack of review, some patches stalled
      * gcc10 patches
      * bit operations (may be postponed to next release)
      * cleanup resources on shutdown
      * windows memory management
      * __rte_internal for ABI checks
        * high priority and not very active now, looking for volunteer
    * CI failures are not taken into account
      * Failures are ignored until maintainer points, this is not scalable
      * **We will be more strict and failing patches will be blocked**
        * If there is a false positive author should send note about it
          * In long term false positives will be fixed
    * graph library
      * No major blocking issue, trending to be merged in this release
      * There will be a new version
      * Thomas will review it
    * tracing library
      * Some concerns on the API, it is copy/paste of log API
      * Lacking more reviews
    * ifproxy library
      * Will be postponed to next release
    * telemetry and rawdev patches are in the backlog

* next-net
  * Pulled from sub-trees and some patches merged
  * It is progressing, there are ~60 patches in backlog, nothing big
  * New igc PMD reviewed, waiting for changes
  * ABI issues with mlx PMD should be resolved before next pull

* next-crypto
  * Test for security API and bbdev patchset are under review

* next-eventdev
  * pull request sent, no more patches expected for -rc1

* next-virtio
  * There will be reviews this week
  * Tree was not active for a while but may prepare a pull request based
    on merged patches

* next-net-intel
  * Two series merged, reviews are going on

* next-net-mlx
  * Some series merged and pulled to next-net

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

* LTS

  * 18.11.7-rc1 is out, please test
    * http://inbox.dpdk.org/dev/20200320193403.18959-1-ktraynor@redhat.com/
      * RedHat, Intel & Mellanox sent test reports
    * Release planned for 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 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-09 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 12:42 Ferruh Yigit [this message]
2020-04-09 13:10 ` Jerin Jacob
2020-04-09 13:36   ` Thomas Monjalon
2020-04-09 13:47     ` Jerin Jacob

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=0e082fc8-c60c-f62b-ef22-4b453e193567@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).