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>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 15/11/2018
Date: Thu, 15 Nov 2018 18:46:48 +0000
Message-ID: <b2841022-4703-44c4-9ce0-023f81115c85@intel.com> (raw)

Minutes 15 November 2018

* Dates
* RC3 status
* Subtrees
* Bugzilla
* OvS
* Conferences

* 6Wind
* Intel
* Mellanox
* RedHat

Release Dates

* RC1 was out on Monday, 29 October.
* RC2 was out on Tuesday, 6 November.
* RC3 was out on Tuesday, 13 November.
* RC4 date is *Monday, 19 November*
* RC5 data is *Thursday, 22 November*
* Release date *pushed out* to *Saturday, 24 November*

* 19.02 dates discussion on mail list:
  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

RC3 status

* Intel test results look good, no blockers, now new high issues
* There are existing high issues, working on it
  * One is external memory related, Anatoly is submitted a patch
  * One is performance drop related disabling avx512
    * Identified as GCC issue, Thomas/Ferruh will submit defect to GCC Bugzilla
    * Will go release with drop, will document it in release notes
* RedHat test results
  * 1 issue, bug 76, debugged by Anatoly
    * Could be a RedHat kernel issue
* Broadcom test results:
  * Ajit sent by mail: testing is looking OK so far.


* main
  * Will be more code merges for RC4.

* next-net
  * Will merge from next-net-mlx:
    * Has bug fixes.
    * Hopefully will be ready on Friday, but may be on Sunday.
  * May get i40e shared code update.
  * There are a few various bug fixes to merge.

* next-crypto
  * No patches for RC4.

* next-virtio
  * Will get a patch from vhost-crypto.

* next-eventdev
  * No patches for RC4.

* next-pipeline
  * Will be a python script.

* next-qos


* Ajit sent following status:
  * It has generally been quite since the last few bugs were fixed.


* Kevin sent out 2 patches/fixes - minimal set to get it working
* Ophir sent out an RC3 patchset - based on above with more features
* Request to get as many people as possible testing


* DPDK and OvS US conferences agendas:

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

                 reply	other threads:[~2018-11-15 18:46 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:

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

  git send-email \
    --in-reply-to=b2841022-4703-44c4-9ce0-023f81115c85@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=thomas@monjalon.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git