From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 05/07/2018
Date: Thu, 5 Jul 2018 11:58:43 +0100 [thread overview]
Message-ID: <ac53f15d-58bf-11cf-4d00-d0e6c1d0865c@intel.com> (raw)
Minutes of 5 July 2018
----------------------
Agenda:
* Merge Deadline for 18.08
* Subtrees
* Bugzilla
Participants:
* Intel
* Mellanox
* NXP
* Red Hat
* SuSe
Merge Deadline for 18.08
------------------------
* *RC1* date pushed to *Wednesday 11 July*.
* sub-trees will be pulled on Tuesday 10 July.
* More review needed, patches not reviewed and merged until RC1 deadline won't
able to make into release.
* Patchsets requires more attention are following:
* hot plug failure handle
* enable hotplug on multi-process
* Device querying
* Anatoly's fixes/patches :)
* Most probably "hot plug failure handle" will be merged partially and "enable
hotplug on multi-process" will be postponed to next release. More foundational
changes required for hotplug.
* Possible RC2 date is 20-23 July, need input from test teams.
Subtrees
--------
* main
* More patches to be merged, more review required
* Thomas is off on Monday 9 July
* next-net
* Plan to send a pull-request end of Thursday 5 July
* Ferruh is on holiday on next week, Thomas will pull from vendor-trees for RC1
* next-crypto
* Target sub-trees pull date, Tuesday 10 July
* There are API changes requires more review/input
* Some PMDs may be merged on RC2
* next-virtio
* There are some patches targeting Friday 6 July
* Some patches can target new RC1 deadline
* next-eventdev
* next-pipeline
* next-qos
* No update was given
Bugzilla
--------
* No update was given
* Shreyansh mentioned from a unit test defect, will discuss offline in the mail
list.
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-05 10:58 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=ac53f15d-58bf-11cf-4d00-d0e6c1d0865c@intel.com \
--to=ferruh.yigit@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).