From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: dpdk-techboard <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of April 8
Date: Fri, 10 Apr 2020 11:08:12 +0100 [thread overview]
Message-ID: <09c7cf05-80d1-196d-f200-f2f3f32feec9@intel.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2020-04-08
Attendees:
- Bruce Richardson
- Ferruh Yigit (Chair)
- Hemant Agrawal
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
1) Make build system deprecation
- Make build support will be "removed" on the 20.11 release.
- A "warning" will be put in to make build on the 20.05 (this) release.
- A build abort will be put in to make build on the 20.08 release, which can be
bypassed with an environment variable.
- The current owner of the deprecation process is Bruce.
2) rte_atomic deprecation
- GCC 4.8.5 & Clang 3.4.2 compilers are part of CentOS7 & RHEL7 and these
distros will keep supported, which means those old compilers will be supported.
- Wrappers to let the use of old distros will be discussed offline via email.
3) 'app/test-flow-perf' acceptance will be voted in next meeting.
4) The next meeting will be on April 22 and Honnappa will chair it.
Thanks,
ferruh
reply other threads:[~2020-04-10 10:08 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=09c7cf05-80d1-196d-f200-f2f3f32feec9@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).