From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK Release Status Meeting 21/07/2018
Date: Fri, 22 Jun 2018 12:13:28 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F37DE55@IRSMSX103.ger.corp.intel.com> (raw)
DPDK Release Status Meeting 21/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 21 June 2018
--------------------
Agenda:
* Subtrees
* Bugzilla
* New website
* Reviewathon
* Dates
Participants:
* Intel
* Cavium
* Mellanox
* NXP
* 6Wind
* Broadcom
Subtrees
--------
* Next-Net
* Not many more patches from last week. Will review/merge more this week.
* Removing old offload API. Help needed, Thomas offered.
* Updating CRC offload and updating examples for offload checks in ethdev
are more ethdev related work.
* Next-Crypto
* No new patches applied since last week.
* Investigating compilation issue.
* Will only be able to apply simpler patches until next week.
* Next-virtio
* No update.
* Next-Eventdev
* Issues with patches from Gage Eads @intel.
* Next-Ip-pipeline
* SofNIC patches will be merged through this tree.
* Master -
* Will review pending patches
* Let Thomas know if there are priority patches for review.
Bugzilla
--------
* Ajit Khaparde from Broadcom volunteered to maintain Bugzilla.
* Main task will be to review incoming defects and make sure they are
assigned to the right maintainer.
* We will review new bugs weekly at this call.
New Web Site
------------
* New DPDK website is available: https://www.dpdk.org/
* Many thanks to Thomas.
* Split in 2 entities. The first "main" for Marketing, Events and DPDK related
projects. The second "core" for DPDK only.
* The "main" website:
* Written in Wordpress - Managed by Linux Foundation.
* Request changes on web@dpdk.org
* Core:
* core.dpdk.org maintained by the community
* DPDK Specific
* No mention of other projects - even DTS
* Managed as separate server
* Hugo + Markdown
* Need to update contributing guide to explain workflow
* Looking for a volunteer to try this and write it up.
* All the URLs have changes - old URLs work with redirect. If not let Thomas
know.
Reviewathon
-----------
* We plan a Community Reviewathon, next Tuesday 26th June.
* Community will co-ordinate on IRC.
* Look for announcement of dev mailing list.
18.08 Dates
-----------
* Integration deadline: June 29, 2018. Soon my pretties, soon.
* Release: August 1, 2018.
next reply other threads:[~2018-06-22 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 12:13 Mcnamara, John [this message]
2018-06-26 9:04 ` [dpdk-dev] Reviewathon Ferruh Yigit
2018-06-28 2:32 ` Dan Gora
2018-06-28 8:59 ` Ferruh Yigit
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=B27915DBBA3421428155699D51E4CFE23F37DE55@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).