DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 19/03/2020
Date: Thu, 19 Mar 2020 13:09:49 +0000	[thread overview]
Message-ID: <125a2c37-83a3-48cd-00dd-3caa8c81b77a@intel.com> (raw)

Minutes 19 March 2020
---------------------

Agenda:
* Release Dates
* Subtrees
* OvS

Participants:
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat


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

* v20.05 dates:
  * Proposal/V1 deadline passed, it was on Wednesday 18 March 2020
  * Integration/Merge/RC1:	Friday 17 April 2020
  * Release:			Wednesday 20 May 2020

  * Marvell, Arm, Mellanox & Broadcom already sent roadmap for 20.05, all
    vendors please share the roadmap for the release.


Subtrees
--------

* main
  * V1 deadline closed, review cycle started, ~800 patches in backlog
  * Working on CI for some Arm issues
  * Will continue to work on eal and CI related
  * next-net pulled
  * Windows patches are merged
    * There is a windows roadmap and bi-weekly meetings
      * https://core.dpdk.org/roadmap/windows/
    * More parties are interested in the Windows support
  * There will be an eal update from Thomas that re-organizes the folders

* next-net
  * It is progressing, reviewing/merging gradually.

* next-crypto
  * ipsec-secgw eventmode patches merged
  * There are more patches to review
    * Baseband driver
    * Security test framework
  * Will review/merge more on next week

* next-eventdev
  * No update in the tree

* next-virtio
  * Design discussion going on for DMA-accelerated vhost-user
  * Rest are mostly fix patches

* next-net-intel
  * ~100 patch in backlog, it is busy
  * Two new PMDs, igc & dcf

* next-net-mlx
  * More patches to come, some RFC sent as text, working to make everything
    ready for -rc1

* LTS

  * 18.11.7
    * -rc1 expected towards end of week
    * Release planned for 10 April

  * 19.11.1 released
    * https://mails.dpdk.org/archives/dev/2020-March/160132.html


OvS
---

* Second OVS-DPDK meeting done, thanks Kevin for notes and recording:
  * https://bluejeans.com/s/6wR3z
  * Intel is preparing something to present in next meeting

* Planning to do more test on 19.11.1



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 Thursdays at 8:30 UTC. If you wish to attend just
send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.

                 reply	other threads:[~2020-03-19 13:09 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=125a2c37-83a3-48cd-00dd-3caa8c81b77a@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).