From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>
Subject: DPDK Release Status Meeting 18/10/2018
Date: Thu, 18 Oct 2018 12:08:42 +0100 [thread overview]
Message-ID: <ca06b2fc-4a25-ce40-6334-811bbe0d2edf@intel.com> (raw)
Minutes 18 October 2018
----------------------
Agenda:
* Dates
* Subtrees
Participants:
* Intel
* Mellanox
Release Dates
-------------
* RC1 date *pushed out a week*, it is now *Friday, 26 October 2018*
* RC2 date is *Friday, 2 November 2018*
* Release date is *Tuesday, 20 November 2018*
* RC1 is pushed out in favor of more complete and stable RC1
* 19.02 dates are discussed
* There are a few holidays during release time,
Christmas Holiday: 24-25 December, many people will get whole week off
New Year: 1 January 2019, some will get whole week off
Chinese New Year (Spring Festival): 4-10 February
* Planed to have a *small release*, in favor of 19.05
* Dates will be discussed more detailed on dev mail list, current proposal
* Proposal deadline: 23 November [Yes, just a little after 18.11 release]
* Integration deadline: 14 December
* RC1: 21 December
* Release: 1 February 2019
Subtrees
--------
* main
* There are patches waiting to be pulled.
* A few hash patchsets, asked Bruce to review them
* telemetry patchset, eal API needs more API documentation
* eal and driver updates from Ilya, needs review
* Power patches are in the queue
* IOVA patches are worrying, needs more review
* Some KNI patches are ready for merge
* Thomas is working on hotplug cleanup patches
* They are not tested much yet
* next-net
* Nothing blocking, a few patchset from Thomas, Andrew is reviewing them
* next-crypto
* Thomas will pull from it today
* next-virtio
* Was ready for RC1 and already pulled
* next-eventdev
* next-pipeline
* next-qos
* Pulled, there are a few patches for RC1
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-10-18 11:08 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=ca06b2fc-4a25-ce40-6334-811bbe0d2edf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.