From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 869011E20; Mon, 28 Aug 2017 17:08:26 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Aug 2017 08:04:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,442,1498546800"; d="scan'208";a="129008340" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.24]) by orsmga002.jf.intel.com with SMTP; 28 Aug 2017 08:04:11 -0700 Received: by (sSMTP sendmail emulation); Mon, 28 Aug 2017 16:04:10 +0100 Date: Mon, 28 Aug 2017 16:04:10 +0100 From: Bruce Richardson To: Jerin Jacob Cc: techboard@dpdk.org, dev@dpdk.org Message-ID: <20170828150410.GA23136@bricha3-MOBL3.ger.corp.intel.com> References: <20170827132425.GA11627@jerin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170827132425.GA11627@jerin> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.8.3 (2017-05-23) Subject: Re: [dpdk-dev] [dpdk-techboard] next techboard meeting (29th, August) X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2017 15:08:28 -0000 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