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 14/05/2020
Date: Thu, 14 May 2020 12:13:19 +0100	[thread overview]
Message-ID: <2980eb50-124c-9da8-9927-0678081b652b@intel.com> (raw)

Minutes 14 May 2020

* Release Dates
* -rc2 status
* Subtrees
* Opens

* Arm
* Debian/Microsoft
* Intel
* Mellanox
* Red Hat

Release Dates

* v20.05 dates:
  * -rc2  is released on Tuesday, 12 May
    * https://mails.dpdk.org/archives/dev/2020-May/167394.html
  * -rc3			Friday 18 May 2020
  * -rc4			Thursday 21 May 2020
  * Release pushed to		*Monday 25 May 2020*

* v20.08 proposal dates, please comment:
  * Proposal/V1:		Tuesday, 16 June 2020
  * Integration/Merge/RC1:	Tuesday, 14 July 2020
  * Release:			Friday, 7 August 2020

  * Please send roadmap for the release

-rc2 status

* Intel sent a -rc2 test report, majority of testing completed, no critical
  * https://mails.dpdk.org/archives/dev/2020-May/167715.html


* main
  * Looking patchsets adding __rte_internal to common folder
    * This is good to prevent false positives in ABI and document intention
  * ABI fix for matured API not merged, discussion going on in the mail list
    * OvS is using it but not critical for OvS
    * Blocking some test cases
  * There are couple of coverity fixes
  * Some documentation
    * Good time for deprecation notices
  * Thomas is looking compilation patches and Makefile deprecation
  * gcc10
    * Akhil's fix for crypto looks good, can replace temporary solution
    * Gavin has patch for mbuf, but this stage can be late/risky for complex fix
      * At this stage we can go with disabling warning as temporary solution
    * Ferruh is getting a warning on hash too, will share it
  * We should consider python2 deprecation
    * A deprecation notice already merged
      * https://patches.dpdk.org/patch/65828/

* next-net
  * Some patches merged and sub-trees pulled for -rc3
  * HW rings allocation patch is in backlog, ethdev patch is internal and can go
    in -rc3 but there a few things to clarify, not sure if it will make -rc3

* next-crypto
  * No update

* next-eventdev
  * No update

* next-virtio
  * 4 fixes in the queue, pull request can be ready today
  * Mellanox vdpa patchset postponed, it introduces new APIs
  * More reviews would help
  * Maxime will have less time next month,  will sync with Xiaolong

* next-net-intel
  * 10 fixes in backlog
  * fm10k patchset postponed to next release

* next-net-mlx
  * 10-15 fixes are expected


* Bugzilla is not discussed for a while
  * After issues assigned, there is not much to do for management
  * It can be good to get list of critical issues offline

* Patchwork hit 70K patches, Hemant/Nipun is the winner :)
  * https://mails.dpdk.org/archives/dev/2020-May/167125.html

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-14 11:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 11:13 Ferruh Yigit [this message]
2020-05-14 11:17 ` Ferruh Yigit
2020-05-14 11:49   ` David Marchand
2020-05-15 14:31   ` Kevin Traynor
2020-05-14 13:44 ` Ferruh Yigit
2020-05-15 16:14 ` Thomas Monjalon
2020-05-21  5:47   ` Ajit Khaparde
2020-05-21  8:28   ` Iremonger, Bernard

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2980eb50-124c-9da8-9927-0678081b652b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \


* 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).