From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK Release Status Meeting 02/08/2018
Date: Thu, 2 Aug 2018 12:25:52 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F3C70CD@IRSMSX103.ger.corp.intel.com> (raw)
DPDK Release Status Meeting 02/08/2018
======================================
Minutes from the weekly DPDK Release Status Meeting.
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.
Minutes 2 August 2018
--------------------
Agenda:
* RC2
* RC3
* Deprecation Notices
* FreeBSD
* Release Dates
Participants:
* Intel
* Cavium
* Mellanox
* NXP
* ARM
RC2
---
* Look okay overall from Intel testing.
* Some issues to be resolved in virtio/vhost.
RC3
---
RC3 targeted for Sunday 5th August.
Status of the subtrees:
* Next-Net
* Pull ongoing.
* Pulled virtio.
* Pulling from vendors.
* Next-Crypto
* 1 patch pending to be applied today.
* Next-virtio
* Pulled.
* Next-Eventdev
* No new patches.
* Next-Ip-pipeline
* Up to date.
Deprecation Notices
-------------------
Please ensure all deprecation notices are reviewed and acked:
http://patches.dpdk.org/project/dpdk/list/?q=deprecation
FreeBSD
-------
We are looking for a FreeBSD DPDK maintainer to keep the ports up to date and
fix minor incompatibility issues. Ideally someone who also works with the
FreeBSD community.
Release Dates
-------------
* RC3 targeted for Sunday Aug 5th.
* No RC4, although doc additions and minor cosmetic fixes will be accepted.
* Target release date is Thursday Aug 9th for release.
reply other threads:[~2018-08-02 12:25 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=B27915DBBA3421428155699D51E4CFE23F3C70CD@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
/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).