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 10/09/2020
Date: Thu, 10 Sep 2020 11:23:06 +0100	[thread overview]
Message-ID: <3d4cf1c6-9cb9-7d76-409e-61b9eb647c10@intel.com> (raw)

Meeting minutes of 10 September 2020
------------------------------------

Agenda:
* Release Dates
* Subtrees
* LTS
* Conferences

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


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

* v20.11 dates
  * Proposal/V1:    Friday, 11 September 2020
  * -rc1:           Friday, 9 October 2020
  * -rc2:           Friday, 23 October 2020
  * Release:        Friday, 13 November 2020

  * Nvidia Mellanox, Marvell & Broadcom already sent roadmap, all contributors
    please send roadmap for the release.

  * Reminder, proposal deadline is end of this week.


Subtrees
--------

* main
  * Makefile support dropped
    * Patches merged partially, they will be merged as they get ready
    * All maintainers should check relevant document
      * Documentation change for make remove is big, everyone should support
  * Default git branch changed to 'main'
  * More help/review required for ethdev library changes
    * Specially for rte flow ones
    * We may think about more tree maintainers
      * rawdev can be an option

* next-net
  * ~200 patches
  * Some patches merged and has pulled from some subtrees
  * Some ethdev from previous releases are still open

* next-crypto
  * No update yet, will merge some this week

* next-eventdev
  * no update

* next-virtio
  * There are some patches pending from Nvidia and Intel
  * Will send following before v1 deadline
    * deprecate zero copy as discussed
    * remove the experimental tag from vDPA

* next-net-intel
  * Some patches merged and pulled by next-net

* next-net-mlx
  * Couple of features are coming
    * mirroring/sampling needs to go ethdev
      * There is a different proposal in main repo

* next-net-mrvl, next-net-brcm
  * no update


LTS
---

* 18.11.10-r1 is out, please test
  * http://inbox.dpdk.org/dev/20200907101224.12396-1-ktraynor@redhat.com/
  * Release planned on two weeks

* v19.11.4 released
  * http://inbox.dpdk.org/dev/20200907145718.120980-1-luca.boccassi@gmail.com/


Conferences
-----------

* DPDK Userspace summit 2020 is on September 22 & 23, schedule is online:
  https://events.linuxfoundation.org/dpdk-userspace-summit/program/schedule/
  * Two days, overall 6 hours (2x3) of talks
  * No break between talks



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-09-10 10: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=3d4cf1c6-9cb9-7d76-409e-61b9eb647c10@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).