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 17/12/2020
Date: Thu, 17 Dec 2020 11:36:46 +0000
Message-ID: <079b2070-296a-0b1d-3ba6-d0ec2ae4e359@intel.com> (raw)

Meeting minutes of 17 December 2020
-----------------------------------

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

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


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

* v21.02 dates
   * Proposal/V1:    Sunday, 20 December 2020
   * -rc1:           Friday, 15 January 2021
   * Release:        Friday, 5 February 2021

   * Please send roadmaps, preferably before beginning of the release
     * Thanks to NTT, Huawei hns3, Intel, Red Hat, Marvell, Broadcom
       for sending roadmap


Highlights
----------

* Next two meetings will be cancelled due to holidays. Happy holidays all.


Subtrees
--------

* main
   * Nothing major at this stage
     * Tools patches and several windows patches

* next-net
   * Not high volume, some patches reviewed/merged
   * Bonding patch cleanup with help of Connor
   * What is the status of the Intel packet mirror patch?

* next-crypto
   * Not too many patches in this release, there are two sets in the backlog
     * app: add multi process crypto application
       * This was good to test some APIs
       * Patch from previous release, not updated
     * compress PMD from mlx5
   * enqueue & dequeue callbacks
     * from previous release
     * There were some warnings, new version expected

* next-eventdev
   * No patches in the backlog
   * There is DLB consolidation in the roadmap, waiting for it

* next-virtio
   * Small series only, no big backlog
   * Working on virtio rework

* next-net-mlx
   * Some sets sent, waiting for more

* next-net-brcm
   * A few patches in the backlog and expecting a few more

* next-net-intel
   * Some big sets in the backlog, a few small ones merged

* next-net-mrvl
   * There are armada patches, will be reviewed
   * meson musdk pkg-config update will go in to next-net


LTS
---

* v19.11.6-rc1 is out, please test
   * http://inbox.dpdk.org/dev/20201203093856.299103-1-luca.boccassi@gmail.com/
   * Waiting for test reports, some already received
   * There are some regression reported by Intel, and suggested fix is causing
     regression
     * Release was planned for today but it is postponed one day while waiting
       update on above issues

* v18.11.11 work is going on
   * waiting for backports, request emails sent
     * Good response from accumulated waiting patches for backport
   * Planning to release the -rc today


OvS
---

* DPDK v20.11 is integrated for the coming 2.15 release


Opens
-----

* Asaf shared a draft release process documentation
   * Not ready yet for sending as patch

* Security (CVE) process
   * There is an effort in Intel to find more resources for it

* Inactive maintainers
   * There are some names listed in the maintainers file but they are not active
     anymore, removing their name can help filling those positions.
     * What is the time taken as inactive?
       * No interaction in the mail list for 3 releases?
         * If missing response is blocking a component, it can be taken as
           inactive without waiting 3 releases.
    * It is hard to fill a maintainer position if it is for a vendor driver
      * Should common code and vendor PMDs be treated differently on this?
        * Should we mark PMDs without active maintainer as 'unmaintained'?



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-12-17 11:36 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=079b2070-296a-0b1d-3ba6-d0ec2ae4e359@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