DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 1/11/2018
Date: Thu, 1 Nov 2018 17:55:51 +0000	[thread overview]
Message-ID: <a1809ea8-58f8-f101-27e1-c0842b1184b4@intel.com> (raw)

Minutes 1 November 2018
-----------------------

Agenda:
* Dates
* RC1 status
* Subtrees
* Bugzilla
* OvS
* Conferences
* Opens


Participants:
* Broadcom
* Debian
* Intel
* Mellanox


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

* RC1 was out on Monday, 29 October.
* RC2 date *pushed out* to *Monday, 5 November 2018*
* Release date is *Tuesday, 20 November 2018*

* 19.02 dates discussion on mail list:
  https://mails.dpdk.org/archives/dev/2018-October/116345.html
  Proposed dates copy-paste from above thread:
  * Proposal deadline Friday 23 November 2018
  * Merge deadline    Friday 14 December 2018
  * RC1 release       Friday 21 December 2018
  * RCx + Testing     Friday 25 January  2019
  * Release           Friday  1 February 2019


RC1 status
----------

* Some blocking issues from IOVA raised by system test
  * https://bugs.dpdk.org/show_bug.cgi?id=100, 101, 102, 103
  * These issues are preventing a full System Test validation for Intel
  * Alejandro sent a patch, he noted he will send a new version
    https://patches.dpdk.org/project/dpdk/list/?series=2189
    Waiting for new version
  * Anatoly is reviewing, more review and testing is required

* Bonding segmentation fault
  * Patch sent and acked: https://patches.dpdk.org/patch/47621/

* Some KNI fails
  * Because of new patches, testcases and docs needs to be updated
  * Ferruh will send doc patches


Subtrees
--------

* main
  * Following patches are planned for RC2:
    * C11 atomics in Ring Library
      * Needs more reviews - particularly from Intel
    * Unit test patches require more review
    * FIPs testing tool
    * Compression performance testing tool
      * May slip to next release if can't make on time
    * Rework on L2FWD
      * not much comments, probably will miss the release

* next-net
  * No new features are planned for RC2
  * Merged some patches from mlx and virtio subtrees, there will be more
  * Around 20 patches are waiting but more expected with RC1 testing

* next-crypto
  * Preparing a pull request for Friday

* next-virtio
  * Preparing a pull request for Friday
  * There will be some vhost_crpto fixes from Fan Zhang
  * packed virtqueues won't able to make the RC2

* next-eventdev
* next-pipeline
* next-qos
  *


Bugzilla
--------

* New issues around IOVA, Bugs 100-103 inclusive


OvS
---

* Getting close moving development branch 'dpdk_latest' to 18.08
* Will probably try to integrate 18.11 RC2
* Ophir's patch for RSS key is required [to mlx5]
* Thomas preparing patch to remove experimental tag form some APIS for OvS
  * https://patches.dpdk.org/project/dpdk/list/?series=2210


DPDK Conference
---------------

* There will be a talk review this week for DPDK North America summit


Opens
-----

* Release status meeting is an important forum for coordinating DPDK releases.
  All major contributors to DPDK should have a representative at the meeting


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 me and email and I will send you the invite.

                 reply	other threads:[~2018-11-01 17:55 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=a1809ea8-58f8-f101-27e1-c0842b1184b4@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    /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).