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 22/11/2018
Date: Thu, 22 Nov 2018 18:15:46 +0000 [thread overview]
Message-ID: <32296f32-3333-498c-2605-6e46a4208bea@intel.com> (raw)
Minutes 22 November 2018
------------------------
Agenda:
* Dates
* RC4 status
* Subtrees
* OvS
* Roadmap
Release Dates
-------------
* RC1 was out on Monday, 29 October.
* RC2 was out on Tuesday, 6 November.
* RC3 was out on Tuesday, 13 November.
* RC4 was out on Sunday, 18 November.
* For rest, best effort dates:
* RC5 date is on *Thursday, 22 November*
* Release date is *Saturday, 24 November*
* else (notes start being like code...)
* RC5 date is on *Friday, 23 November*
* Release date is *Monday, 26 November* || *Tuesday, 27 November*
* 19.02 dates are discussed:
* Proposal deadline *pushed out* to *Thursday, 29 November*
* Other deadlines remained same as proposed in mail list
https://mails.dpdk.org/archives/dev/2018-October/116345.html
RC4 status
----------
* Intel test results look good, ready for RC5
* RedHat test results looks good,
* Bug 76, turned out not a DPDK defect but kernel issue
Subtrees
--------
* main
* next-net
* Only main and next-net getting last remaining patches.
* Doc patches will go in RC5
* Please don't forget deprecation notices for 19.02.
OvS
---
* Switched to 18.11-rc3/4 without issue.
Roadmap
-------
* Please all contributors planning to send features for 19.02 send a roadmap!
* Reminder that roadmaps are not commitment but sharing what you are planning to
work on next release, which help a lot for planning and collaboration.
* Intel is working on 19.02 roadmap and will send soon.
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-22 18:15 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=32296f32-3333-498c-2605-6e46a4208bea@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--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).