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 21/05/2020
Date: Thu, 21 May 2020 12:20:05 +0100	[thread overview]
Message-ID: <87e28a30-6122-033a-70b4-bca84538b8cb@intel.com> (raw)

Minutes 21 May 2020
-------------------

Agenda:
* Release Dates
* -rc3 status
* Subtrees
* Opens

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


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

* v20.05 dates:
  * -rc3 is released on Tuesday, 19 May
    * https://mails.dpdk.org/archives/dev/2020-May/168313.html
  * -rc4 pushed to		*Sunday 24 May 2020*
  * Release pushed to		*Tuesday 26 May 2020*

* v20.08 proposal dates *updated*, please comment:
  * Proposal/V1:		Friday, 12 June 2020
  * -rc1:			Wednesday, 8 July 2020
  * -rc2:			Monday, 20 July 2020
  * Release:			Tuesday, 4 August 2020

  * Please send roadmap for the release


-rc3 status
-----------

* Intel testing %80 percent done, can be completed tomorrow
  * Only a PMD issue and a few medium priority defects found
  * Overall looks good


Subtrees
--------

* main
  * Some gcc10 fixes will be merged
    * gcc10 may be causing ABI compatibility issues
  * Started to work on release notes, John will support
    * Good to have tested HW information from all vendors

* next-net
  * Only a few fixes for -rc4
  * Vendor sub-trees has patches, will pull from them today

* next-crypto
  * No update

* next-eventdev
  * No update

* next-virtio
  * No update

* next-net-intel
  * Some fixes in sub-tree already

* LTS

  * A set of security releases done
    * 19.11.2: https://mails.dpdk.org/archives/dev/2020-May/168103.html
    * 18.11.8: https://mails.dpdk.org/archives/dev/2020-May/168110.html
    * 20.02.1: https://mails.dpdk.org/archives/dev/2020-May/168102.html


Opens
-----

* Fuzz testing can be used capture some security issues in advance.
  * This can be done in the CI.
  * Luca shared oss-fuzz as reference:
    * https://oss-fuzz.com/
    * https://github.com/google/oss-fuzz



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-05-21 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 11:20 Ferruh Yigit [this message]
2020-05-21 11:24 ` Ferruh Yigit

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=87e28a30-6122-033a-70b4-bca84538b8cb@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).