From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 67D1BA0C50; Fri, 16 Jul 2021 16:51:56 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BEFE44067B; Fri, 16 Jul 2021 16:51:55 +0200 (CEST) Received: from mail-pj1-f43.google.com (mail-pj1-f43.google.com [209.85.216.43]) by mails.dpdk.org (Postfix) with ESMTP id 605ED40151 for ; Fri, 16 Jul 2021 16:51:54 +0200 (CEST) Received: by mail-pj1-f43.google.com with SMTP id g24so6574818pji.4 for ; Fri, 16 Jul 2021 07:51:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=3kQag7L7EVWU/+4gZEY9i8bUDyHcCiw9MqQHmSfRWSk=; b=CZDYxuJEDTDKweLZg+EO8KX0GXwt4xYDXQdU72p4MqgtI3wwlRBBbnMQSngAkz5Uib ugtX17GyCLGkkz3B+kt8A9RcW/P7u5mu0c87JewsUS45CvzazLct9fOGODtyllkOlB5E RC2YPLnL3I/FVYvhPwbVTFlBkFAgY7Rc4ojo4fVAC0178eVTEfk+/MLkkyIkjlCZfraJ pEzqNdqKM1cZFOtV/LUiCBeCKVApE8cyaiLLshpa3ZWYb8PZvMGuQJbET80e2rzNT00D PhtX1l2FtSs3jbe0Guff7sypg64DQDSq3VYA+fjwaKoDivw1ArTTpqbuY6bwaDcbvuqn Ax7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=3kQag7L7EVWU/+4gZEY9i8bUDyHcCiw9MqQHmSfRWSk=; b=PEdH/uSdsSKCo9ovkq+cxHCKNQ7udhI+f1ORMtvUJecTwENo378QxneIxAcZeRQDCj fekPCM3idfSrsEE3xQrXAxkJvmwc3o0OAiCi4ezI/Stuhh5wxvoBCCvuk/wu9ZIR7r0G thVqc+sp7MLNbbwXgPdjIxTtQr+ytqT7I9ats5Al+GEUcsNqCtsZf0d7CD0+ZpbsHYIl Ys+w1Egu5xmZocLjHqRMAePL3pBvrDO0CvMlRd8d3FCPTKVz55X4dckhBZuhiRB44flE c7E2kfRlprNxeVp5d8CWZ2+yd73xTgQFBAxaSm/dea1lB684kO/eMI67lmHPeKJ89P15 KrrA== X-Gm-Message-State: AOAM532ZOgGeZMyd1HqNrRJGoJKH/0Grv1V2bvrcgvcF0FjuCj7IHsZu V/ft1CIArPYcz9mHES10VteXBP/L3IIKEA== X-Google-Smtp-Source: ABdhPJwZSD4XDi6xP8q+0jpwPPRhnUwNYofYwHT6EO/UELfugMQDeNZcqZ+rVnYg91rRDcoEJndi9w== X-Received: by 2002:a17:90a:9ab:: with SMTP id 40mr16043426pjo.9.1626447112994; Fri, 16 Jul 2021 07:51:52 -0700 (PDT) Received: from hermes.local (204-195-33-123.wavecable.com. [204.195.33.123]) by smtp.gmail.com with ESMTPSA id p17sm12327843pjg.54.2021.07.16.07.51.52 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 16 Jul 2021 07:51:52 -0700 (PDT) Date: Fri, 16 Jul 2021 07:51:49 -0700 From: Stephen Hemminger To: dev@dpdk.org Message-ID: <20210716075149.034dce20@hermes.local> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] Minutes of Technical Board Meeting 2021-06-02 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Minutes of Technical Board Meeting, 2021-06-02 ============================================== NOTE: The technical board meetings every second Wednesday at https://meet.jit.si/DPDK at 3 pm UTC. Meetings are public, and DPDK community members are welcome to attend. NOTE: Next meeting will be on Wednesday 2021-06-09 @3pm UTC, and will be chaired by Thomas. 1/ CI infrastructure -------------------- The current CI infrastructure is failing. The root cause appears to be the upgrade by UNH IOL causing test failures. The test failures impact the patch approval process since patches marked as failing CI are normally not allowed. Proposal was to have another set of resources to test upgrade before deploying. 2/ ABI stability period ----------------------- When initially discussed the stability period was going to be two years, but in final compromise a trial period of one year was agreed to but the wording in documentation allows for longer periods. In the documentation (guides/contributing/abi_policy.rst) "Major ABI versions are declared no more frequently than yearly" The proposal is to go to two year period but there are some open concerns that need addressing: - several data structures and inline functions need to be hidden to reduce the exposed ABI. - many experimental features need to be moved to stable status. - deprecated functions and fields need to be removed. If 21.11 is going to have two year ABI window, then cleanups are needed. Related discussions: Should the scope of Long Term Stable (LTS) be expended? Right now, the scope is limited to bug fixes. Vendors and distro's using LTS would appreciate having new drivers (and PCI ids). What about backporting standalone new libraries to LTS? Conclusion: is that more discussion about requirements and risks are needed before expanding LTS. Indirect results of the current ABI policy has benefits. The ABI clamp has acted to reduce wild/unstable changes and causes better designs. Downside is that there is less of a trial window for changes, if a new feature requires ABI change it goes into the yearly release without getting longer period of review and testing. What kind of upcoming features need ABI breakage? Conclusion: Taskforce will be setup to make a more concrete recommendation. The taskforce will give status update in 2 weeks (next TAB) and recommend action for 21.11 in one month.