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 25/06/2020
Date: Thu, 25 Jun 2020 12:49:02 +0100	[thread overview]
Message-ID: <e4fe1b15-ebd6-e85b-5a09-b65870afb96f@intel.com> (raw)

Minutes 25 June 2020
--------------------

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

Participants:
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* 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


Subtrees
--------

* main
  * Window porting progressing
    * Core library support, mempool, mbuf & ethdev planned for this release
      * A PMD for windows planned for 20.11
  * -rc1 deadline looks short considering roadmap features
    * Need more reviews
    * Some features may be dropped if not reviewed
  * Jerin will review Mellanox multicast patch
    * https://mails.dpdk.org/archives/dev/2020-June/169943.html

* next-net
  * Only some patches merged this week, pulled from vendor sub-trees
  * There are still some ethdev patches
  * Big shared code updates from Intel waiting is a concern

* next-crypto
  * Started reviews
  * There is DOCSIS patches under review
  * Will try to merge some on this week
  * If compressdev maintenance takes too much effort we can consider separating
    it
    * Not much activity as of now, Mellanox may send some patches
    * bbdev also in Akhil's bucket, we may consider separating that based on
      work load

* next-eventdev
  * Waiting a new version of Intel DLB PMD
    * If there are API changes, having it late may cause missing the release
  * Will merge some patches next week

* next-virtio
  * vhost improve ready state patchset discussion is going on
  * vDPA API and framework rework, rebased and send a new version
  * Chenbo/Ferruh will cover during absence of Maxime


LTS
---

* v19.11.3 released
  * https://mails.dpdk.org/archives/dev/2020-June/170820.htmlesult

* v18.11.9-rc1 is out, please test
  * https://mails.dpdk.org/archives/dev/2020-June/170888.html
  * The planned date for the final release is 3rd July.
  * Microsoft testing it, will send the report


OvS
---
 * 2.14 Release feature deadline (soft deadline) is approaching
  (beginning of July)


Opens
-----

* We may check ABI documentation if it requires clarification

* Testing
  * There is a new hire in the community lab
    * Will extend DTS for testing
    * Will start with basic ethdev testing

* A change in the recent kernels are causing crash with vfio
  * The kernel side commit:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=abafbc551fddede3e0a08dee1dcde08fc0eb8476
    * The kernel side commit seems merged for v5.8-rc1
  * Fix in DPDK:
    http://inbox.dpdk.org/dev/20200625035046.19820-1-haiyue.wang@intel.com/

* Defects
  * Ajit prepared a Bugzilla report

* Meeting on "meet.jit.si/DPDK" going fine, will continue with it



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-06-25 11:49 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=e4fe1b15-ebd6-e85b-5a09-b65870afb96f@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).