From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of January 2
Date: Wed, 16 Jan 2019 10:55:06 +0100 [thread overview]
Message-ID: <22768085.QYr4furZkP@xps> (raw)
Meeting notes for the DPDK technical board meeting held on 2019-01-02
Attendees: 7/9
- Ferruh Yigit
- Jerin Jacob
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
1) Mentoring
Stephen will check Google Code and other possible initiatives.
Project scope must be well defined, useful, easy to ramp up and testable.
Idea of projects: automatic testing of vhost/virtio or Hyper-V.
AWS and Azure can be some targets.
Project suggestions will be discussed on the mailing list.
We are looking for mentors. Maxime proposed to mentor vhost/virtio testing.
2) Deprecation process
- How new API or ABI is introduced
No need to require introducing new code in RTE_NEXT_ABI ifdef
while sending deprecation notice.
Instead, a draft of the new code (RFC patch) must be submitted
and referenced in the deprecation notice.
So the deprecation notice may be better discussed before giving ack,
and the users can prepare their application for the next DPDK release.
- How old API is removed
We must not remove a deprecated API if the replacement is still experimental.
It is recommended to remove deprecated APIs after a LTS release.
The process change must adjusted by Ferruh. Initial proposal was sent:
https://patches.dpdk.org/project/dpdk/list/?series=2927
3) Next techboard meeting
- It will be on January 16
- Bruce Richardson will chair it
reply other threads:[~2019-01-16 9:55 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=22768085.QYr4furZkP@xps \
--to=thomas@monjalon.net \
--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).