From: "Wiles, Keith" <keith.wiles@intel.com>
To: Olivier MATZ <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] next techboard meeting (13th, October)
Date: Wed, 11 Oct 2017 12:41:10 +0000 [thread overview]
Message-ID: <E87EB44E-06BA-4927-AC8C-3A7C2A6A9B09@intel.com> (raw)
In-Reply-To: <20171011093618.hfvaftsqz6ihnph5@platinum>
> On Oct 11, 2017, at 4:36 AM, Olivier MATZ <olivier.matz@6wind.com> wrote:
>
> Hi all,
>
> The next techboard meeting will happen on IRC #dpdk-board, at 3pm UTC,
> this friday 13th of october.
>
> The agenda is updated here:
> https://annuel.framapad.org/p/r.0c3cc4d1e011214183872a98f6b5c7db
>
>
> 1) ABI stability:
> - one LTS per year
> - 17.11 to be a LTS
> - every new API has the "experimental" tag
> - 3 Acks are needed for deprecation and they should come from different companies
> reference: http://dpdk.org/ml/archives/dev/2017-October/077937.html
> reference: http://dpdk.org/ml/archives/dev/2017-October/077935.html
I assume the person or company that pushes the notice can be one of the ACKs is this correct?
Also does the ACK need to come from a person working for a company or can this person be an independent developer? Maybe a very minor point, but someone that is working for a company could Ack independent of the company if so stated. Just be careful how you word the requirement, something like ‘Only one Ack per company or independent developer’
>
> 2) update on license discussion concerning the optimized version of 64bit division
> code from libdivide
> - any feedback from governing board?
>
> 3) update on IPSec offload (rte_security)
> - the conclusion on this topic was to post concerns/proposals on dpdk-dev
> - is there still something expected from techboard?
>
> Olivier
Regards,
Keith
next prev parent reply other threads:[~2017-10-11 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 9:36 Olivier MATZ
2017-10-11 12:41 ` Wiles, Keith [this message]
2017-10-11 12:48 ` [dpdk-dev] [dpdk-techboard] " Thomas Monjalon
2017-10-11 12:53 ` Wiles, Keith
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=E87EB44E-06BA-4927-AC8C-3A7C2A6A9B09@intel.com \
--to=keith.wiles@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--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).