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 13/02/2020
Date: Thu, 13 Feb 2020 11:20:33 +0000	[thread overview]
Message-ID: <3bec5581-7ccf-cdf3-5461-562c18cbbc31@intel.com> (raw)

Minutes 13 February 2020
------------------------

Agenda:
* Release Dates
* -rc2 status
* Subtrees
* OvS

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


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

* v20.02 dates:
  * -rc2 is released on 6 February
    * https://mails.dpdk.org/archives/dev/2020-February/157366.html
  * -rc3			Friday 14 February 2020
  * Release			Friday 21 February 2020
    * Release pushed because of extended PRC holidays

* v20.05 *updated* proposal, please comment:
  * Proposal/V1:		Wednesday 18 March 2020
  * Integration/Merge/RC1:	Friday 17 April 2020
  * Release:			Wednesday 20 May 2020

  * The update request is based on delays in 20.02
  * Release date postponed more taking into PRC holiday on 1-5 May into account


-rc2 Status
-----------

* -rc2 has been released last week, but it has not been fully tested by Intel
  because of extended PRC holiday, expecting to have a test report tomorrow.
  No issue reported from Mellanox testing.

* !! Can all vendors/contributors that tested the -rc1/-rc2 please share their
  test results, either via email to mail list or in the release status meeting,
  to increase our confidence to the release.

* Decided go on with the existing -rc3 plan, but if we find late critical issues
  because of delayed testing, we may need to have interim -rc4/-rc5 releases.

* There is still some risk around release date, based on full validation output.


Subtrees
--------

* main
  * Sub-trees are not ready yet, will pull them tomorrow for -rc3
  * ABI fixes merged
  * ACL patches under review
  * Windows patches has been merged
  * Lots of doc updates for -rc3 & -rc4
    * Reminder of deprecation notices, some discussed but not sent yet
  * Should be ready for -rc3 tomorrow

* next-net
  * Some fixes merged, pulled from sub-trees, will ready for -rc3 end of today
  * Will pull from mlx and virtio trees when they are ready today
  * af_xdp fix series reviewed by @Xiaolong, will merge today
  * Pulling from -brcm & -mrvl trees as well regularly

* next-net-crypto
  * Only a couple of patches left for -rc3
    * Doc patch for inline protocol
    * One test crypto patch waiting reply from @Fiona

* next-net-eventdev
  * No update

* next-net-virtio
  * There will be a few more fixes for -rc3, waiting @Ivan

* next-net-intel
  * Some fixes merged for -rc3

* next-net-mlx
  * Some small fixes merged for -rc3, there will be a few more

* LTS

  * 19.11.x
    * Started working on 19.11.1, going smooth for now
    * Will wait 20.02 release for having a -rc1 date
    * Proposed to create 19.11 branch in stable tree

  * 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 issue resolved
    * Waiting ETA for QAT issue until end of today
      * If no update received, will proceed with the release

  * 18.11.x
    * Started to work on next LTS version 18.11.7


OvS
---

* 2.13 release should be around this week
* The experimental tag dropped in master may remain as experimental in LTS
  This means the OvS may have to keep consuming API as experimental, DPDK
  discussion thread on the issue:
  * https://mails.dpdk.org/archives/dev/2020-February/157149.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-02-13 11:20 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=3bec5581-7ccf-cdf3-5461-562c18cbbc31@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).