From: Bruce Richardson <bruce.richardson@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: techboard@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-techboard] next techboard meeting (29th, August)
Date: Mon, 28 Aug 2017 16:04:10 +0100 [thread overview]
Message-ID: <20170828150410.GA23136@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <20170827132425.GA11627@jerin>
On Sun, Aug 27, 2017 at 06:54:35PM +0530, Jerin Jacob wrote:
> Hi All,
>
> The next meeting of the tech board will happen on IRC #dpdk-board, at 3pm UTC, on 29th of August(Tuesday)
>
> Agenda:
>
> 1) Discussion on next tree requests
> a) Next tree for IPSec offload and maintainership
> http://dpdk.org/ml/archives/dev/2017-August/072995.html
> b) Next tree for cli
> http://dpdk.org/ml/archives/dev/2017-August/073343.html
>
> 2) Approval of a policy for changes to the minimum DPDK requirements.
> e.g. like what was done with bumping IA min to SSE4.2 in last release.
>
Proposal for a policy for this item, so as to hopefully speed up the
discussion at the meeting:
* Updates to the minimum HW requirements, i.e. those dropping support for
hardware which was previously supported, should be treated as an ABI
change, and follow that deprecation policy. Specifically:
- change announced at least one release in advance
- patches removing support for the older hardware should have at least
three ACKs before being applied.
Regards,
/Bruce
next prev parent reply other threads:[~2017-08-28 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 13:24 Jerin Jacob
2017-08-28 15:04 ` Bruce Richardson [this message]
2017-08-29 15:30 ` Jerin Jacob
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=20170828150410.GA23136@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.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).