From: Yuanhan Liu <yliu@fridaylinux.org>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of July 05
Date: Mon, 10 Jul 2017 13:25:28 +0800 [thread overview]
Message-ID: <20170710052527.GF11626@yliu-home> (raw)
Hi all,
Here is the meeting notes for the last DPDK technical board meeting
held on 2017-07-05.
Member attendees:
- Hemant Agrawal
- Jan Blunck
- Jerin Jacob
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
- Yuanhan Liu
0. Release blocking issues
No major issues, but as always, we lack of reviews.
1. Check action points from minutes of last meeting
- The repo for the new build system is created.
- Dom0 support will be marked as deprecated this release and be removed in
the next release (v17.11).
2. Release backups
Thomas proposed to have some release backups [0], so that there is always
someone to take this role in case of accident or long vacations. And the
board approves to let Ferruh Yigit and Yuanhan Liu be the release backups.
Note it's not for sharing Thomas load; it's just backups.
[0]: http://dpdk.org/ml/archives/dev/2017-June/069229.html
3. Next meeting
Hemant will chair.
reply other threads:[~2017-07-10 5:25 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=20170710052527.GF11626@yliu-home \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=techboard@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).