From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK Release Status Meeting 06/07/2018
Date: Wed, 13 Jun 2018 20:43:37 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F36D071@IRSMSX103.ger.corp.intel.com> (raw)
DPDK Release Status Meeting 06/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 6 June 2018
-------------------
Agenda:
* New Patchwork v2.
* Roadmaps.
* Upcoming changes from Tech Board meeting.
* Proposal deadline.
* Backlog of old patches.
* Proposal Deadline.
* Memory rework.
* Applying patches to master.
* Subtrees.
Stable
* Testing from Intel ongoing.
* Mellanox: 17.11 + 18.02.
* RedHat: putting testing in place.
Participants:
* Intel
* Mellanox
* RedHat
* Broadcom
New Patchwork version.
* Patchwork upgraded to V2.0.2 - Thanks Thomas, Mellanox and Stephen Finucane.
* Now supports "Series" i.e., patchsets for new patches.
* New client available that supports applying a full patch series:
git-pw: http://patchwork.readthedocs.io/projects/git-pw/en/latest/
Roadmaps
* All contributing companies are encourages to send updated roadmaps for
18.08 and later: http://dpdk.org/dev/roadmap
* Intel, Mellanox and Broadcom committed to sending updates.
Upcoming changes from Tech Board meeting.
* Explicit time limits for reviews/commits. Acked patches will be committed
within 2 weeks. This has already been agreed previously and documented:
http://dpdk.org/doc/guides/contributing/patches.html#steps-to-getting-your-patch-merged
There was a new recommendation that non-acked, non-commented files will
be committed after 3 weeks if there are no objections/comments.
* Weekly merge. Subtrees to be merged on Thursdays. Master on Friday.
Backlog of old patches.
* There is a backlog of old patches:
http://dpdk.org/dev/patchwork/project/dpdk/list/?order=date
Need help cleaning this updated
Proposal Deadline
* 8 June
* Other dates: http://dpdk.org/dev/roadmap#dates
Memory rework
* Thomas reported that Mellanox are still seeing issues
* Will interface with Anatoly
* Will check with OvS
Applying patches to master
* Looking for patches to apply early.
* HyperV patches will be applied.
Subtrees
* Net: Not many patches yet
* Virtio: Quiet for now.
* Crypto: Nothing merged yet. 62 patches in the backlog.
Stable
* Testing from Intel ongoing.
* Mellanox: 17.11 + 18.02.
* RedHat: putting testing in place.
reply other threads:[~2018-06-13 20:43 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=B27915DBBA3421428155699D51E4CFE23F36D071@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).