From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] Minutes of technical board meeting 2018-02-14
Date: Wed, 21 Feb 2018 09:29:16 +0100 [thread overview]
Message-ID: <20180221082916.5ocnwvvpqjuobqe4@glumotte.dev.6wind.com> (raw)
Hi,
Here are the minutes of the last DPDK technical board meeting held on
2018-02-14.
Attendees: 6 members among 9 were present, which is less than the quorum
(70% of the Technical Board):
- Ferruh Yigit
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
1) Acknowledge Yuanhan Liu resignation from vhost/virtio maintenance and
replacement by Maxime Coquelin
First the techboard would like to thanks Yuanhan for his great job on
vhost and virtio.
The new virtio tree maintainer Maxime has been approved by the
techboard (quorum reached by mail for this point). We are confident
that Maxime is the right person.
2) Review remaining deprecation notices for 18.02
The only one that remaining was the deprecation notice for kernel
version: https://dpdk.org/dev/patchwork/patch/34778/
There is no consensus yet about which kernel versions should be
supported. The latest upstream LTS kernel is 3.16, but some
distributions maintain kernels based on older ones.
It has been decided to drop this patch for 18.02, and take the
decision for 18.05. The discussion continues on the mailing list.
3) Contribution guideline for dependent work
https://dpdk.org/dev/patchwork/patch/33250/
As explained in the patch description, the contributions with
dependent work require a special attention. Enforcing the dependent
work:
- reduces maintenance
- keeps the code consistent
But:
- can prevent contribution, because there is too much work
- it not always possible because requiring special knowledge
For large contributions, the techboard shall provide guidelines on a
case by case basis.
To enforce the changes:
- at the beginning of the release cycle, the objectives are highlighted
(ex: all libraries should use the new xxx api instead of yyy). This
can be repeated in RC1 announcement.
- after 2 or 3 releases, the PMDs or libraries that do not follow the
recommendations are disabled.
Next Meeting:
- 2018-02-28 @ 3pm UTC
- Stephen to chair discussion as per alphabetical order
- Rediscuss 3) with quorum
reply other threads:[~2018-02-21 8:29 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=20180221082916.5ocnwvvpqjuobqe4@glumotte.dev.6wind.com \
--to=olivier.matz@6wind.com \
--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).