DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of August 1
Date: Mon, 06 Aug 2018 13:32:56 +0200	[thread overview]
Message-ID: <5270721.be8s8OCcRt@xps> (raw)

Meeting notes for the DPDK technical board meeting held on 2018-08-01

It was a very short meeting without agenda.
Several members were not present or active.

1/ Kevin Traynor did a comment about experimental API which can be forgotten
and not be promoted as stable API.
It is OK to keep API experimental during several releases.
Promoting an API is a decision of the maintainers.

2/ There are some deprecation notices to review.
It can block the release 18.08.

Next meeting will be on August 15th and Bruce will chair it.

                 reply	other threads:[~2018-08-06 11:32 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=5270721.be8s8OCcRt@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).