From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7C71B4A63; Fri, 15 Dec 2017 10:11:57 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 4E3FA397D for ; Fri, 15 Dec 2017 10:11:56 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B105220BDF; Fri, 15 Dec 2017 04:11:55 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 15 Dec 2017 04:11:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= mesmtp; bh=f4GjfqPdAwGoWkQ764SB4CBg32r5lG0iEZSYNi9ZDow=; b=bmOaw wkQu8idYsTDNZk/XL0RuCm2Jp1EcR9D4FCxaqJK5KzN/cuck9Rt7dtyvEPqkeOba qzotXeZkisZfOzgK/42du9fufdxXXu5bHxprmgErvjjA0eIFkuldPYV7YjcyXP69 zSDKai+WAkJIep8h9as0PoF8VO1sbrJvnpyaw8= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=f4GjfqPdAwGoWkQ764SB4CBg32r5l G0iEZSYNi9ZDow=; b=GsH5v404VI+TDa/MwL/mW494Rq+ZxQSb3SKaHK1Qzawf0 PERGYoPLZ3kVbpEpXTRU7qjlAs4UTZ7jFcn4hlpPyeLXx71aSo+vcAqHbmTNM+kU QOkqI/8oNk2dL8ZXW0+rQUDwiU0qLG8AaYjPnS1ckd58qu+KHW6YMAvjboovp3yK pl69LwNAcBJ3z7LnnI1LyJl2GP9MfcOeUrLWNnKHnRHRkJELmwdVlaPhtc+6cPZD 5cx5n2b5+VMZndNYsne6F7mMkEPc5zqQCv/9v4g0aEHu2QI8O0GEBopAI21Z1nkA gJblCehUNkZv4flIJknXc6nolALtEyotKn05w5OIQ== X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 613E87E17D; Fri, 15 Dec 2017 04:11:55 -0500 (EST) From: Thomas Monjalon To: announce@dpdk.org Cc: qian.q.xu@intel.com Date: Fri, 15 Dec 2017 10:11:54 +0100 Message-ID: <3581801.9Iet7LyEFa@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: announce@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list Errors-To: announce-bounces@dpdk.org Sender: "announce" Subject: [dpdk-dev] [dpdk-announce] A Bug in DPDK? Use Bugzilla! X-BeenThere: dev@dpdk.org List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Dec 2017 09:11:57 -0000 Hi, As announced during the last summits at Dublin and San Jose, an instance of Bugzilla is available on dpdk.org: https://dpdk.org/tracker/ We should use Bugzilla to keep track of bugs and resolutions. The code maintainers are expected to register on Bugzilla, in order to be assigned an notified of bugs in their area. The bug manager is Qian Xu (thank you). Note: the feature requests should be done on the mailing list and recorded on the roadmap page when planned: http://dpdk.org/dev/roadmap PS: this message is sent on the announce mailing list and forwarded on the dev mailing list. Please use only dev@dpdk.org for comments and discussion. Thank you