From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK Release Status Meeting 26/07/2018
Date: Thu, 26 Jul 2018 10:52:17 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F3C0F88@IRSMSX103.ger.corp.intel.com> (raw)
DPDK Release Status Meeting 26/07/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 26 July 2018
--------------------
Agenda:
* Subtrees
* RC1
* RC2
* Release Dates
* Compilation Testing/Issues
* Bugzilla
* Userspace
Participants:
* Intel
* Cavium
* Mellanox
* NXP
* Debian
* Broadcom
Subtrees
--------
* Next-Net
* Ready to pull.
* Next-Crypto
* Merged to master.
* Next-virtio
* Some patches/fixes for memory issues need to be applied.
Tiwei to merge.
* Next-Eventdev
* Patchset/PR ready.
* Next-Ip-pipeline
* Patchset/PR ready.
* Master
* Will merge patchset for autotest.
* Waiting for virtio patches.
* Will merge up to RC2 today.
RC1
---
* Fixes/patches submitted for issues identifies as High and Medium during
testing.
RC2
---
* RC2 target was Wednesday 25th July.
* New RC2 target is Thursday 26th July.
* Virtio memory related patches and fixes.
* Tiwei will push to virtio subtree.
* Will sync on IRC with Thomas.
* Qian will send a list of fix patches.
Release Dates
-------------
* RC2 target is Thursday 26th July.
* RC3 should be next Thursday Aug 2nd.
* If that is stable we may skip RC4 and go to release.
* Target release date is Wednesday Aug.
Compilation testing
-------------------
* FreeBSD 10.0 removed from compilation since it is deprecated.
* Will add FreeBSD 11.x instead.
* Docs need to be updated to reflect these changes. John to investigate.
* In the next release we should decide as a community what OS and kernel
versions will be supported. We should also discuss this at DPDK Userspace
Dublin.
* We should prepare patches for 18.11 with supported versions.
* We should also look at any upcoming issues with GCC 9.
* Pablo will run compilation test for Thomas prior to RC2.
* Luca, from Debian, highlighted the SuSE open build service that we could
potentially use to test packaging:
https://openbuildservice.org/
https://build.opensuse.org/
* NXP have tested 18.08-RC1 builds and will report back on any issues in RC2.
Bugzilla
--------
* Issue from the last 7 days:
https://bugs.dpdk.org/buglist.cgi?chfieldfrom=7d
Userspace
---------
* DPDK Userspace, Dublin September 5-6:
https://www.dpdk.org/event/dpdk-userspace-dublin-2018/
* Call for Papers closes Friday 27th July:
https://docs.google.com/forms/d/e/1FAIpQLSd5hfn58cTKWBcBO_eK6qKWAA5cG9BpPhBWZR_FMLIrgZKWuQ/viewform
reply other threads:[~2018-07-26 10:52 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=B27915DBBA3421428155699D51E4CFE23F3C0F88@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).