From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 26/9/2019
Date: Thu, 26 Sep 2019 13:52:11 +0100 [thread overview]
Message-ID: <0d21509e-2d74-86aa-0b33-c557df41daf3@intel.com> (raw)
Minutes 26 September 2019
-------------------------
Agenda:
* Release Dates
* Subtrees
* OvS
* Opens
Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Red Hat
Release Dates
-------------
* v19.11 dates:
* Proposal deadline passed, it was on 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
* There is a PRC holiday on October 1-7
* Proposed dates for 20.02 release on the mail list, please comment
https://mails.dpdk.org/archives/dev/2019-September/143311.html
Subtrees
--------
* main
* David will be co-maintaining the main branch
* There are two weeks to the rc1, patcwork looks busy
* next-net
* Andrew's ethdev patchsets has been merged
* ~250 patches in backlog, some may be pushed to rc2
* It will be good if we can do an early merge to master branch this week
* next-net-virtio
* Reviews are going on, no risk
* next-net-intel
* Some ice shared code has been merged, more to go
* There are some ethdev dependencies, pinged for review
* next-net-mrvl
* Some patches will be merged next week, no risk
* next-eventdev
* Will merge patch this week and next week, no risk
* Marvell planning to submit, two eventdev applications
* One separate l2fwd-event app and update the existing l3fwd to add support
for eventdev.
* LTS
* v18.11.3-rc1 is under test
* Microsoft and Intel sent reports
* Target release date is 9 October
* v17.11.7-rc1 is under test
* Intel testing reported issues
* Some fixes merged for the reported issues, mostly minor issues
* There won't be an -rc2, release will be this week
OvS
---
* Intel is pushing multi-seg TSO support
* A patch may be required in DPDK vhost side
* dpdk_latest branch lagging behind master, Ian will take care
Open
----
* Please check Coverity and Bugzilla defects
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 an email to "John McNamara <john.mcnamara@intel.com>" for the invite.
next reply other threads:[~2019-09-26 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 12:52 Ferruh Yigit [this message]
2019-09-26 13:05 ` David Marchand
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=0d21509e-2d74-86aa-0b33-c557df41daf3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--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).