From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Bernard Iremonger <bernard.iremonger@intel.com>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 5/9/2019
Date: Thu, 5 Sep 2019 13:50:27 +0100 [thread overview]
Message-ID: <1fc64c48-e769-af1b-ecc5-bb9e5b532260@intel.com> (raw)
In-Reply-To: <967b2b42-ca6a-b2a4-14d9-36093660e150@intel.com>
On 9/5/2019 12:10 PM, Ferruh Yigit wrote:
> Minutes 5 September 2019
> ------------------------
>
> Agenda:
> * Release Dates
> * V1 Status
> * Subtrees
> * Conferences
>
>
> Participants:
> * Arm
> * Debian/Microsoft
> * Intel
> * Marvell
> * Mellanox
> * Red Hat
>
>
> Release Dates
> -------------
>
> * v19.11 dates:
> * Proposal/V1 Friday 06 September 2019
> * Integration/Merge/RC1 Friday 11 October 2019
> * Release Friday 08 November 2019
>
> * Marvell, Intel, Arm & Mellanox has sent roadmaps, thanks,
> everyone planning to contribute in this release please send roadmaps
> to help planning.
>
> * Will put v19.02 proposal into mail list for discussion, it is challenging
> because of Christmas and Spring holidays overlap with the release dates.
>
> * Need input from all contributors in next week about the scope/size of the
> v19.02 to help planning 19.02 dates.
s/19.02/20.02/g
Thanks Bernard for notifying!
>
>
> V1 Status
> ----------
>
> * V1 deadline is a few days away, end of this week. 800+ patches in patchwork.
>
>
> Subtrees
> --------
>
> * main
> * Patchwork looks busy
> * Please all sub-tree maintainers update 'delegate' fields
> * There is a plan for automated delegation, will be manual for now
> * There will be an early merge end of this week
> * Ping Thomas for high priority patches
>
> * next-net
> * Only a few patches has been merged, reviews are going on
> * There are two new PMDs, 'ppfe' from NXP and 'hns3' from Huawei
> * There are ethdev APIs patches from Andrew which look like will be big one
>
> * next-net-virtio
> * Reviews are going on, Maxime and Tiwei are reviewing
> * Looks a little busier than normal
>
> * next-net-intel
> * Reviews are going on, Xiaolong is working on them
>
> * next-eventdev
> * Marvell planning to submit, two Eventdev applications.
> * One seperate l2fwd-event app and update the existing l3fwd to add support
> for Eventdev.
>
>
> Conferences
> -----------
>
> * Reminder: DPDK Summit NA CFP deadline September 6th
> https://mails.dpdk.org/archives/announce/2019-August/000276.html
>
> * OvS conference won't be co-located with DPDK summit this year
>
>
> 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.
>
prev parent reply other threads:[~2019-09-05 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 11:10 Ferruh Yigit
2019-09-05 12:50 ` Ferruh Yigit [this message]
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=1fc64c48-e769-af1b-ecc5-bb9e5b532260@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@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).