From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id AAF5F9E7 for ; Tue, 14 Feb 2017 17:22:38 +0100 (CET) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga105.fm.intel.com with ESMTP; 14 Feb 2017 08:22:37 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.35,162,1484035200"; d="scan'208";a="65068119" Received: from irsmsx110.ger.corp.intel.com ([163.33.3.25]) by fmsmga005.fm.intel.com with ESMTP; 14 Feb 2017 08:22:37 -0800 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.77]) by irsmsx110.ger.corp.intel.com ([169.254.15.101]) with mapi id 14.03.0248.002; Tue, 14 Feb 2017 16:22:35 +0000 From: "Mcnamara, John" To: Thomas Monjalon CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v1] doc: update release notes for 17.02 Thread-Index: AQHShteiGAOW1U5RwkqbQLTaC+u8PqFopp2AgAAHGUA= Date: Tue, 14 Feb 2017 16:22:35 +0000 Message-ID: References: <1487086372-11630-1-git-send-email-john.mcnamara@intel.com> <1551253.KADGnDBYIu@xps13> In-Reply-To: <1551253.KADGnDBYIu@xps13> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZTQ0MjkwYzUtNDc2OC00ZmVjLWIzYmQtMTZkNmM3MzhhYjcxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6Iks2anVMd1N5MFhZMDhQYWdGdThxamt6YkEwS2dxdFZSNW9EK2h4V3BqUkk9In0= x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v1] doc: update release notes for 17.02 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: Tue, 14 Feb 2017 16:22:39 -0000 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Tuesday, February 14, 2017 3:51 PM > To: Mcnamara, John > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH v1] doc: update release notes for 17.02 >=20 > 2017-02-14 15:32, John McNamara: > > -Resolved Issues > > ---------------- > > - > > -.. This section should contain bug fixes added to the relevant > sections. Sample format: > > - > > - * **code/section Fixed issue in the past tense with a full stop.** > > - > > - Add a short 1-2 sentence description of the resolved issue in the > past tense. > > - The title should contain the code/lib section like a commit > message. > > - Add the entries in alphabetic order in the relevant sections > below. > > - > > - This section is a comment. do not overwrite or remove it. > > - Also, make sure to start the actual text at the margin. > > - =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > - > > - > > -EAL > > -~~~ > > - > > > > Drivers > > ~~~~~~~ > > > > * **net/virtio: Fixed multiple process support.** > > > > - Fixed few regressions introduced in recent releases that break the > > virtio > > + Fixed a few regressions introduced in recent releases that break > > + the virtio > > multiple process support. > > > > > > -Libraries > > -~~~~~~~~~ > > - > > - > > Examples > > ~~~~~~~~ > > > > * **examples/ethtool: Fixed crash with non-PCI devices.** > > > > - Querying a non-PCI device was dereferencing non-existent PCI data > > - resulting in a segmentation fault. > > + Fixed issue where querying a non-PCI device was dereferencing > > + non-existent PCI data resulting in a segmentation fault. >=20 > It looks strange to remove the "Resolved Issues" heading while keeping > content. > I think we could totally remove them as most of the fixes are not > documented here anyway. You are right. That was a mistake on my side, I meant to leave the heading. However, now that you mention it, it doesn't look good that we have a "Resolved Issues" section with just 2 fixes. I don't think they capture the range of fixes in this release. Maybe we need to be more disciplined with including information in the Release Notes when non-trivial fixes are submitted. In this case I'll put back in the "Resolved Issues" heading and submit a v2= . John