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 29/10/2020
Date: Thu, 29 Oct 2020 12:22:37 +0000
Message-ID: <87a098f2-f48a-92dc-4944-0e2f2cd2a796@intel.com> (raw)

Meeting minutes of 29 October 2020
----------------------------------

Agenda:
* Release Dates
* -rc1 status
* Subtrees

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


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

* v20.11 dates
   * -rc2 pushed to      *Tuesday, 3 November 2020*
   * -rc3:               Thursday, 12 November 2020
   * Release:            Wednesday, 25 November 2020


-rc1 status
-----------

* Intel test report shared, many issues reported but no critical/showstopper
   issue:
   https://mails.dpdk.org/archives/dev/2020-October/189618.html

* Red Hat sent a test report, all looks good
   https://mails.dpdk.org/archives/dev/2020-October/189872.html


Subtrees
--------

* main
   * Thomas was busy with mbuf patchset, please review
     * https://patches.dpdk.org/project/dpdk/list/?series=13454
     * https://patches.dpdk.org/project/dpdk/list/?series=13416
   * Power patchset eal part can be merged to enable DLB eventdev drivers
     * The ethdev patch requires new version with more documentation
       * Ferruh & Jerin will try to review the ethdev patch
   * fibs patchset merged
   * Working on
     * Ring series from Honnappa
     * replace blacklist/whitelist with allow/block from Stephen
   * There is a makefile for the kmods repo, please review
     * https://patches.dpdk.org/patch/79999/
   * There is a GSO API behavior change without deprecation notice
     * https://patches.dpdk.org/patch/82163/
     * Requires techboard approval
   * There is a patch to add MMIO support to PIO map
     * Can it be handled in virtio level? more review please
     * https://patches.dpdk.org/project/dpdk/list/?series=13220

* next-net
   * Andrew was covering next-net for past a few days
   * Will get ethdev patch to remove legacy filter support
     * https://patches.dpdk.org/project/dpdk/list/?series=13207&state=*
       * There is a dependency to tep-term example removal
         * https://patches.dpdk.org/patch/82169/
     * https://patches.dpdk.org/project/dpdk/list/?series=13211&state=*
   * Will pull from all sub-trees

* next-crypto
   * Merged most of the patches, 7-8 left
   * enqueue & dequeue callback functions series from Intel remaining
     * Was suspicions that it can be ABI break
     * Will ask for new version
     * Planning to merge if there is not objection

* next-eventdev
   * Waiting new version for DLB PMDs
     * eal libraries may be merged very soon, if so new version can be done
       as rebased on top of it
     * Need the new version soon (today/tomorrow), to be able to review and
       merge it for the -rc2

* next-virtio
   * Pull request sent for -rc2
   * No more patch expected for -rc2

* next-net-intel
   * Some patches already merged and waiting for pull

* next-net-mlx
   * There can be more features for -rc2
   * Some patches already merged and waiting for pull

* next-net-mrvl
   * There will be two more patches for -rc2, they will be processed soon

* next-net-brcm
   * Some patches already merged and waiting for pull



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-10-29 12:23 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=87a098f2-f48a-92dc-4944-0e2f2cd2a796@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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git