From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: nd <nd@arm.com>, nd <nd@arm.com>
Subject: [dpdk-dev] DPDK techboard minutes of November 20th
Date: Mon, 16 Dec 2019 16:45:33 +0000 [thread overview]
Message-ID: <VE1PR08MB5149B96E2387104DACAA2E9D98510@VE1PR08MB5149.eurprd08.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2019-11-20
Members Attending
-----------------
-Bruce
-Ferruh
-Hemant
-Honnappa (Chair)
-Kevin
-Konstantin
-Maxime
-Olivier
-Stephen
-Thomas
NOTE: The technical board meetings every second Wednesday on IRC channel #dpdk-board, at 3pm UTC. Meetings are public and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2019-12-04 @3pm UTC, and will be chaired by Kevin Traynor
1) ABI version number for experimental libraries DPDK 19.11 = ABI 20 libs 19.11 = .so.20.0 Pure experimental libs in 19.11 = .so.0.200
For pure experimental libs, the version will be updated for every release to allow for installation of multiple versions of DPDK.
2) Changes to DPDK community lab at UNH were discussed. No conclusion was made.
3) Procedure to request for addition to the security vulnerability pre-release mailing list need to be published on dpdk.org to make it more visible.
Thank you,
Honnappa
reply other threads:[~2019-12-16 16:45 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=VE1PR08MB5149B96E2387104DACAA2E9D98510@VE1PR08MB5149.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
/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).