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 30/01/2020
Date: Thu, 30 Jan 2020 12:16:16 +0000	[thread overview]
Message-ID: <f570e5f4-db29-6024-8eed-695a0447da39@intel.com> (raw)

Minutes 30 January 2020
-----------------------

Agenda:
* Release Dates
* -rc1 status
* Subtrees
* OvS
* Opens

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


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

* v20.02 dates:
  * -rc2 pushed to		*Wednesday 5 February 2020*
  * -rc3			Monday 10 February 2020
  * Release pushed to		*Wednesday 19 February 2020*
    * Release pushed because of extended PRC holidays

* v20.05 dates:
  * Proposal/V1:		Friday 6 March 2020
  * Integration/Merge/RC1:	Friday 10 April 2020
  * Release:			Friday 1 May 2020


-rc1 Status
-----------

* No new major/critical issue reported


Subtrees
--------

* main
  * Windows patches waiting for new version, if they are ready they can be
    merged to -rc2
  * Will merge more patches this afternoon and tomorrow
  * ABI tooling will be ready for -rc2
    * meter library breaks the ABI and needs fixing before release

* next-net
  * Nothing interesting, mostly fixes for -rc2
  * There is a big mlx patchset in the queue, mlx tree will be ready
    today/tomorrow
  * mlx vdpa patchset is waiting for review from Maxime

* next-net-crypto
  * armv8 crypto patch merged
  * Vilademir send a new version for SAD patchset which reduces the performance
    drop
  * SAD patch discussed in techboard, functionality has priority in sample
    applications, so patchset can proceed with existing performance drop.
  * CPU crypto will be reviewed if there is enough time, -rc2 being pushed may
    provide required time for review and if it is ready it will be considered
    for -rc2
  * There is an ABI break in crypto tree, waiting input from Fiona, will try to
    solve it, if not will revert the commit causing it

* next-net-eventdev
  * no update

* next-net-virtio
  * Will get fixes for -rc2
  * virtio vdpa postponed to next release

* LTS

  * 17.11.10-rc1 released, please test and report results
    * https://mails.dpdk.org/archives/dev/2020-January/154915.html
    * Got test results from Intel, Red Hat & Mellanox
      * QAT regression reported by Intel testing, need help from developers
      * mlx reported regressions, needs more details
    * Will wait two more week for above issues clarified
      * Rough release date is mid February

  * 18.11.6-rc2 released, please test and report results
    * https://mails.dpdk.org/archives/dev/2020-January/155132.html
    * It has been confirmed regressions reported in -rc1 fixed in -rc2
    * OvS completed testing with -rc2, no issue found
    * Release expected sometime this week


OvS
---

* Validated LTS releases, they are good to go
* 2.13 release expected on mid February


Opens
-----

* Coverity run last week, there are outstanding issues, please check:
https://scan.coverity.com/projects/dpdk-data-plane-development-kit?tab=overview
  * John sent email to individuals whose patch causing a Coverity issue
    But everyone is welcome to fix the issues listed

* For information, icc compiler support reduced by technical board, warning
  disabling will be done in global level and having warnings will be allowed



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-01-30 12:16 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=f570e5f4-db29-6024-8eed-695a0447da39@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).