From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,URIBL_SBL,URIBL_SBL_A autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9AB1BC0650F for ; Tue, 30 Jul 2019 11:16:54 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 5ABB820693 for ; Tue, 30 Jul 2019 11:16:54 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5ABB820693 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 807991C0B5; Tue, 30 Jul 2019 13:16:53 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 445711C0AA for ; Tue, 30 Jul 2019 13:16:52 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jul 2019 04:16:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,326,1559545200"; d="scan'208";a="190839454" Received: from irsmsx154.ger.corp.intel.com ([163.33.192.96]) by fmsmga001.fm.intel.com with ESMTP; 30 Jul 2019 04:16:50 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.45]) by IRSMSX154.ger.corp.intel.com ([169.254.12.160]) with mapi id 14.03.0439.000; Tue, 30 Jul 2019 12:16:49 +0100 From: "Mcnamara, John" To: "Yigit, Ferruh" , "Kovacevic, Marko" CC: "dev@dpdk.org" , Thomas Monjalon , Maxime Coquelin Thread-Topic: [PATCH 1/2] doc/security: clarify pre-release end of the embargo date Thread-Index: AQHVJSav0DwgKxo2xUGHLx2Hz4kXFKbjRjew Date: Tue, 30 Jul 2019 11:16:50 +0000 Message-ID: References: <20190617160648.8506-1-ferruh.yigit@intel.com> In-Reply-To: <20190617160648.8506-1-ferruh.yigit@intel.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTJkNjMzNDUtY2Y0YS00MTIxLWI2OTMtNmQ3Njc4ZjY2ZWRhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiS2s1SklxRFR4VVwvWkczbHdPNVZJelg2ZGRHckY5QlRKRUFoWXU3cUowUm5aSVlaNU04bzlTaEF1SUZGMVpBTGsifQ== dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 1/2] doc/security: clarify pre-release end of the embargo date 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" > -----Original Message----- > From: Yigit, Ferruh > Sent: Monday, June 17, 2019 5:07 PM > To: Mcnamara, John ; Kovacevic, Marko > > Cc: dev@dpdk.org; Thomas Monjalon ; Maxime Coquelin > > Subject: [PATCH 1/2] doc/security: clarify pre-release end of the embargo > date >=20 > Clarify that a fixed date will be used for end of embargo (public > disclosure) date while communicating with downstream stakeholders. >=20 > Initial document got a review that it gives an impression that > communicated embargo date can be a range like 'less than a week' which is > not the case. The range applies when defining the end of the embargo date > but a fix date will be communicated. >=20 Acked-by: John McNamara