From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 12/07/2018
Date: Thu, 12 Jul 2018 12:47:49 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F8F9634@IRSMSX107.ger.corp.intel.com> (raw)
Minutes of 12 July 2018
-----------------------
Agenda:
* Merge Deadline for 18.08
* Subtrees
Participants:
* Intel
* Mellanox
* NXP
* Cavium
Merge Deadline for 18.08
------------------------
* *RC1* date pushed to *Friday 13 July*.
* "Enable hotplug on multi-process" will not be included in 18.08, due to insufficient reviews
* Some patchsets require more attention:
* Memory patches from Anatoly
* Some fixes from Hotplug patchset, which will be extracted from the set and merged in 18.08.
* RC2 date targeting 24-25 July.
Subtrees
--------
* main
* More patches to be merged, more review required
* next-net
* Subtree was pulled this week
* Other patches have been applied to the other subtrees (next-net-intel/next-net-mlx).
* Thomas might get more patches directly from these subtrees for RC1
* next-crypto
* Subtree was pulled this week
* All library changes have been applied
* QAT Compression PMD still needs to be applied, so it will be done before RC1 is out
* Other PMDs will be merged in RC2
* next-virtio
* Subtree was pulled this week
* next-eventdev
* Subtree was pulled this week
* next-pipeline
* Some issues need to be resolved before the subtree can be pulled for RC1.
* next-qos
* No update was given
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-07-12 12:48 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=E115CCD9D858EF4F90C690B0DCB4D8977F8F9634@IRSMSX107.ger.corp.intel.com \
--to=pablo.de.lara.guarch@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).