From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: DPDK Techboard <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of March 27
Date: Tue, 2 Apr 2019 10:43:24 +0200 [thread overview]
Message-ID: <70e56c73-17a0-735a-5dc3-4ce0521afa50@redhat.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2019-03-27.
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
1) Drop short-term stable releases unless volunteers
From now on, call for volunteer to maintain and validate short-term
release will be done in the release announce e-mail. If nobody
volunteered one month after the release announce, the branch will be
closed. Thomas to send an e-mail to announce the new process.
2) Next long-term stable branch maintenance
Luca Boccassi will maintain the v19.11 LTS branch.
3) Next-crypto and cryptodev trees maintenance
Thomas will send an e-mail to most active crypto contributors to
request for help in reviews and maintenance. Ruifeng Wang from ARM
might help with the tree maintenance.
4) Next technical board representative at governing board
Maxime Coquelin will represent the technical board at the governing
board for the next quarter.
5) Un-implemented API deprecation and removal
The technical board acknowledges the current plan[0] to deprecate un-
implemented APIs in DPDK v19.05 release and remove them in v19.08.
6) Vulnerability management process
First draft of the process is under review. Experts from Intel, Red Hat,
Mellanox, Microsoft and Linux Foundation have already commented it. Next
version will be published publicly.
7) Next technical board meeting (April 10th)
Olivier Matz will chair it.
[0]: https://mails.dpdk.org/archives/dev/2018-December/122213.html
next reply other threads:[~2019-04-02 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 8:43 Maxime Coquelin [this message]
2019-04-02 8:43 ` Maxime Coquelin
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=70e56c73-17a0-735a-5dc3-4ce0521afa50@redhat.com \
--to=maxime.coquelin@redhat.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).