From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] technical board meeting, 2017-06-07
Date: Tue, 6 Jun 2017 09:40:30 -0700 [thread overview]
Message-ID: <20170606094030.0198e5c6@xeon-e3> (raw)
Hello everyone,
A meeting of the DPDK technical board will occur this Wednesday, 7th June 2017
at 3pm UTC.
The meeting takes place on the #dpdk-board channel on IRC.
This meeting is public, so anybody can join, see below for the agenda.
Agenda: https://annuel.framapad.org/p/r.0c3cc4d1e011214183872a98f6b5c7db
0. Release blocking issues?
Are there any known urgent blocking issues at this time.
1. Hosting and user repositories
What is policy? Where should it be documented?
2. Bus changes and API breakage.
I haven't been tracking the fine print. How badly does next
release change the API?
4. Fail-Safe PMD
What is current status? Is it ready?
5. Bugzilla
Last meeting agreed to setup Bugzilla, what is progress.
6. Governing board status
Are there any AR's for TAB?
next reply other threads:[~2017-06-06 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 16:40 Stephen Hemminger [this message]
[not found] ` <CGME20170607094545eucas1p2d77d683df268c13561a5f6fe42526778@eucas1p2.samsung.com>
2017-06-07 9:45 ` Ilya Maximets
2017-06-07 11:18 ` Bruce Richardson
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=20170606094030.0198e5c6@xeon-e3 \
--to=stephen@networkplumber.org \
--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).