From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of September 11
Date: Thu, 12 Sep 2019 18:46:32 +0200 [thread overview]
Message-ID: <2094778.IvcVR4htMB@xps> (raw)
Meeting notes for the DPDK technical board meeting held on 2019-05-08
Attendees: 9/9
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
1/ Review of last meeting minutes
Starting now the meeting minutes should be drafted
in the next 24 hours after the meeting.
It has been decided that meeting minutes are agreed
if no objection one week after the draft is shared.
2/ Examples removal
Bruce and Hemant will start removing few useless examples
during 19.11 release cycle.
3/ ABI compatibility
The new ABI policy has been discussed for months
and will be a topic for a panel discussion in Bordeaux event.
The final version and agreement of the guidelines are expected soon.
The first step should start after 19.11 release,
and will forbid any change which is not ABI-compatible with 19.11.
This first period must be used to prepare a longer freeze.
Then it will be allowed to break ABI compatibility in release 20.11,
and a longer compatibility period (2 years) could start from 20.11.
Note that experimental functions can change at any time.
4/ Build systems
Meson support is almost complete.
Bruce will present the status in Bordeaux event.
Makefile system will be deprecated in the release 19.11,
and there will be a blocking warning in the default configuration
of the release 20.02. The date for Makefile removal has not been decided.
The configurability of current Meson integration needs to be discussed.
5/ Next techboard meeting will be face to face
in Bordeaux, on September 19 Thursday, at 9pm.
reply other threads:[~2019-09-12 16:53 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=2094778.IvcVR4htMB@xps \
--to=thomas@monjalon.net \
--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).