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 25/10/2018
Date: Thu, 25 Oct 2018 10:27:30 +0100 [thread overview]
Message-ID: <35f70b27-a8f0-6a36-f67d-9081d752aac9@intel.com> (raw)
Minutes 25 October 2018
-----------------------
Agenda:
* Dates
* Subtrees
* Bugzilla
Participants:
* 6wind
* Debian
* Intel
* Mellanox
* NXP
* RedHat
Release Dates
-------------
* RC1 date is unchanged, it is *Friday, 26 October 2018*
* RC2 date is *Friday, 2 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
Subtrees
--------
* main
* There are some big sets waiting, please help reviewing them:
* power
- Waiting for processing
* telemetry
- Latest version sent recently, should be OK
* kni
- There are two sets, should be OK, Ferruh to check
* ring C11
- Needs more input, Olivier will try to review
* hash
- Multiple patchets, most of them acked by Bruce
* IOVA
- More review required, Ferruh to ping for reviewers
* rte_pause
* nanosleep
* unit tests
- Some may go in rc2
* global variables
- Cleanup, if not able to make rc1 will wait next release
* next-net
* Nothing blocking, will pull from next-net-mlx
* next-crypto
* Pulled, new patches may go in master directly
* next-virtio
* No action for rc1, more patches can go in later
* next-eventdev
* next-pipeline
* next-qos
*
Bugzilla
--------
* No showstopper reported
* Bug 97,
* Issue and fix provided by Yongseok
* Will work on alternative solution, target is to fix 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-25 9:27 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=35f70b27-a8f0-6a36-f67d-9081d752aac9@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).