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 30/07/2020
Date: Thu, 30 Jul 2020 11:37:10 +0100	[thread overview]
Message-ID: <be752276-e4e6-cc16-7ec2-ac4146cf4175@intel.com> (raw)

Minutes 30 July 2020
--------------------

Agenda:
* Release Dates
* -rc2 status
* Subtrees
* LTS
* Opens

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


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

* v20.08 dates:
  * -rc3 pushed to *Thursday, 30 July 2020*
  * -rc4:	    Wednesday, 5 August 2020
  * Release         Friday, 7 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

  * Please remember to send roadmap for 20.11.


-rc2 status
-----------

* Intel finished testing, mostly good except two critical defects
  * A driver TSO issue, fix merged
  * vhost performance drop
    * Maxime's patch verified, will be merged for -rc3
    * Interrupt issue will be worked in next release


Subtrees
--------

* main
  * Worrying that there is no more fixes for libraries
  * Will close the -rc3 today
  * More review required for examples, please help
    * https://patches.dpdk.org/project/dpdk/list/?q=example
  * -rc4 will be for documentation patches
    * Need to finalize the deprecation notices
      * Please check the ABI improvements for 20.11, and send
        required deprecation notices.
        * There are already lots of deprecation notice for 20.11
          It is worrying that 20.11 will be too big
        * Data hiding and struct splitting already planned for ethdev
          Same can be applied for other device abstraction layers,
          Please check and send deprecation notices.
    * John will be back next week, may support for final doc reviews
  * There is a public holiday on Monday in Ireland
  * Please all maintainers cleanup the patchwork before release

* next-net
  * Pulled from vendor sub-trees and some fixes merged
  * There is a last minute bnxt patch, will check for -rc3
  * No more patches expected for release

* next-crypto
  * Pull request merged
  * There are deprecation notices in backlog

* next-eventdev
  * Pull request merged
  * There can be a few critical patches for -rc3
    * May send another pull request, will close today

* next-virtio
  * Performance fix and some other fixes merged
  * Pulled by next-net, no more patch expected for release

* next-net-mlx, next-net-intel
  * Pulled for -rc3

* next-net-mrvl
  * Qede patches postponed to next release
  * No more patch expected for release

* next-net-brcm
  * There is a patchset merged in sub-tree
  * Ajit will check if they are fixes or can be postponed


LTS
---

* 19.11.4 work is going on
  * Some patches are backported, email sent, please review

* 18.11.10 work is going on
  * Some patches are backported


Opens
-----

* Bugzilla
  * Nothing critical for the release
  * Three new defects to Intel, some are to old releases
  * There are open defects needs attention
    * Intel pulled some defects to internal to address them
      * No visible change in the Bugzilla



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-30 10:37 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=be752276-e4e6-cc16-7ec2-ac4146cf4175@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).