From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: DPDK techboard minutes of January 2 Date: Wed, 16 Jan 2019 10:55:06 +0100 Message-ID: <22768085.QYr4furZkP@xps> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: techboard@dpdk.org To: dev@dpdk.org Return-path: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Meeting notes for the DPDK technical board meeting held on 2019-01-02 Attendees: 7/9 - Ferruh Yigit - Jerin Jacob - Konstantin Ananyev - Maxime Coquelin - Olivier Matz - Stephen Hemminger - Thomas Monjalon 1) Mentoring Stephen will check Google Code and other possible initiatives. Project scope must be well defined, useful, easy to ramp up and testable. Idea of projects: automatic testing of vhost/virtio or Hyper-V. AWS and Azure can be some targets. Project suggestions will be discussed on the mailing list. We are looking for mentors. Maxime proposed to mentor vhost/virtio testing. 2) Deprecation process - How new API or ABI is introduced No need to require introducing new code in RTE_NEXT_ABI ifdef while sending deprecation notice. Instead, a draft of the new code (RFC patch) must be submitted and referenced in the deprecation notice. So the deprecation notice may be better discussed before giving ack, and the users can prepare their application for the next DPDK release. - How old API is removed We must not remove a deprecated API if the replacement is still experimental. It is recommended to remove deprecated APIs after a LTS release. The process change must adjusted by Ferruh. Initial proposal was sent: https://patches.dpdk.org/project/dpdk/list/?series=2927 3) Next techboard meeting - It will be on January 16 - Bruce Richardson will chair it