From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 03168A04C2; Wed, 12 Aug 2020 11:52:22 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DEF2C1C127; Wed, 12 Aug 2020 11:52:21 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 28F3E1C10B; Wed, 12 Aug 2020 11:52:19 +0200 (CEST) IronPort-SDR: DYXO/lFcimeeUspmAkEpwzJPy1tXUoGfNB5DvYLOJfEbPEYXAhU+qHmJEx6xpKxeIN0Vpi7PUM ZAqcD1cC4xQA== X-IronPort-AV: E=McAfee;i="6000,8403,9710"; a="133977081" X-IronPort-AV: E=Sophos;i="5.76,303,1592895600"; d="scan'208";a="133977081" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 12 Aug 2020 02:52:19 -0700 IronPort-SDR: UKfa4fBCt3Ry2+ILa17CIeE5vOfBAlZBfjC8x5lr7Iu1e5QtclXuu+jPemR3rhtEewIeBuGNo7 tIucnDiCqITw== X-IronPort-AV: E=Sophos;i="5.76,303,1592895600"; d="scan'208";a="469766431" Received: from bricha3-mobl.ger.corp.intel.com ([10.255.202.43]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 12 Aug 2020 02:52:14 -0700 Date: Wed, 12 Aug 2020 10:52:09 +0100 From: Bruce Richardson To: Thomas Monjalon Cc: "Dybkowski, AdamX" , "Trahe, Fiona" , "dev@dpdk.org" , "Zhang, Roy Fan" , "stephen@networkplumber.org" , "Burakov, Anatoly" , "bluca@debian.org" , Akhil Goyal , "Mcnamara, John" , techboard@dpdk.org Message-ID: <20200812095209.GA312@bricha3-MOBL.ger.corp.intel.com> References: <20200727094113.2849-1-adamx.dybkowski@intel.com> <5056132.gDXpgoo2J5@thomas> <3567036.vTBxH0KFj1@thomas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3567036.vTBxH0KFj1@thomas> Subject: Re: [dpdk-dev] [PATCH] doc: scheduler API deprecation notice 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Aug 10, 2020 at 02:50:57PM +0200, Thomas Monjalon wrote: > 10/08/2020 13:49, Trahe, Fiona: > > Sorry about that Thomas, Akhil, we should have chased up acks sooner. > > > > Given the proposed content of the patch, and the similar changes that are recommended and agreed > > throughout DPDK do you think an exception can be made and that this change can get into 20.11 even > > without the deprecation notice being in 20.08? > > That's a question for techboard. > > PS: please avoid top-posting > My initial 2c is that we should allow this, and add the required deprecation notice to the online docs immediately. I would assume most people use the online docs rather than building their own from the package, therefore adding in a deprecation notice to the online versions a few days after a release should not be a major problem IMHO. Also, given the fact that we have once-a-year at most to apply ABI changes, and this is the first time we are going this, so I think a little latitude should be given! :-)