From: Ferruh Yigit <ferruh.yigit@intel.com>
To: <techboard@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2021-08-11
Date: Mon, 16 Aug 2021 10:34:43 +0100 [thread overview]
Message-ID: <e62610f7-56b6-9070-cb55-43596f3ec971@intel.com> (raw)
In-Reply-To: <e600e472-2b39-7f07-d20e-9d6fe8e6d515@intel.com>
Minutes of Technical Board Meeting, 2021-08-11
Members Attending: 8/12
- Aaron Conole
- Ferruh Yigit (Chair)
- Hemant Agrawal
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Stephen Hemminger
NOTE: The Technical Board meetings take place every second Wednesday
on https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
NOTE: Next meeting will be on Wednesday 2021-08-25 @3pm UTC,
and will be chaired by Hemant.
#1 Extending stable ABI / API to two years
* No decision given yet, left decision to next meeting.
* Can continue executing the tasks listed in the excel sheet during v21.11
#2 Documenting criteria on adding/removing members to technical board
* Document needs further reviews, please review.
* Will set a deadline for the document review in next meeting.
#3 Atomic API
* Atomic built-ins used because of old compilers.
* If we can drop old compiler support, we can switch to atomic APIs.
* Discussion to drop RHEL7 is going on in the mail list.
#4 Exception path sample app
* No objection to have the sample app in principal.
* Details and design can be discussed more when patches are available.
#5 github repo access for extending CI for Arm support
* Honnappa and Aaron will figure out the details on what is exactly required
* Later we can crate an policy around it, right now it is for
Thomas/Aaron/Honnappa to manage.
parent reply other threads:[~2021-08-16 9:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <e600e472-2b39-7f07-d20e-9d6fe8e6d515@intel.com>]
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=e62610f7-56b6-9070-cb55-43596f3ec971@intel.com \
--to=ferruh.yigit@intel.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).