From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: Bug tracker for DPDK
Date: Thu, 27 Aug 2015 10:46:37 -0700
Message-ID: <20150827104637.111e4871@urahara>
References: <B27915DBBA3421428155699D51E4CFE2022FD0EA@IRSMSX103.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "dev@dpdk.org" <dev@dpdk.org>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com
 [209.85.220.41]) by dpdk.org (Postfix) with ESMTP id 9FE64591A
 for <dev@dpdk.org>; Thu, 27 Aug 2015 19:46:26 +0200 (CEST)
Received: by pacdd16 with SMTP id dd16so32659155pac.2
 for <dev@dpdk.org>; Thu, 27 Aug 2015 10:46:26 -0700 (PDT)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2022FD0EA@IRSMSX103.ger.corp.intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Thu, 27 Aug 2015 10:28:45 +0000
"Mcnamara, John" <john.mcnamara@intel.com> wrote:

> Hi,
> 
> Now that we are at the start of a release cycle it is a good time to talk about the need for a bug tracker for DPDK.
> 
> As well as tracking defects it could be used to track upcoming or desired features/fixes.
> 
> The most obvious tool for this is Bugzilla but other suggestions or ideas are welcome:
> 
>     https://www.bugzilla.org/
> 
> John.

The problem with bug trackers is everyone has agree to use it.
Which is why Linux kernel developers treat bugzilla as read-only.