From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: DPDK Techboard <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of May 20th
Date: Thu, 21 May 2020 22:10:30 +0100 [thread overview]
Message-ID: <6653586a-4ed2-af32-4e91-62dc0b9196a6@redhat.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2020-05-20
TB Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
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.
1) v20.05 items
- For release notes:
-- Deprecations to be reviewed
-- Tested Hw to be listed
2) Experimental versioning options
- Background mail http://inbox.dpdk.org/dev/2199673.OYXXYNVTWy@thomas
- This is about how libs with only experimental API are versioned
- At present there is a separate versioning scheme for them
- It has caused some extra maintainence
- Proposal is to remove the special experimental versioning scheme
- It does not impact status of experimental, just versioning
- Experimental status can be indicated in:
-- lib name/versioning
-- prog guide
-- MAINTAINERS file
-- doxygen
- Voted to remove special numbering scheme for experimental libs
3) Governing board rep
- Bruce will take over
- Will be rotated quarterly
4) Testpmd maintainership
- No news from companies about possible maintainers
5) Security pre-release members
- Out of time
- Will be voted by email
Next meeting will be on Wednesday 2020-06-04 @3pm UTC, and will be
chaired by Konstantin Ananyev
reply other threads:[~2020-05-21 21:10 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=6653586a-4ed2-af32-4e91-62dc0b9196a6@redhat.com \
--to=ktraynor@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).