From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: tools brainstorming Date: Mon, 23 Mar 2015 16:38:17 -0700 Message-ID: <20150323233817.GA9077@mhcomputing.net> References: <3571725.20GtF5MAnU@xps13> <0C5AFCA4B3408848ADF2A3073F7D8CC86D53E553@IRSMSX109.ger.corp.intel.com> <1823253.PAnM90fukl@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev-VfR2kkLFssw@public.gmane.org To: Thomas Monjalon Return-path: Content-Disposition: inline In-Reply-To: <1823253.PAnM90fukl@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Mon, Mar 23, 2015 at 05:18:49PM +0100, Thomas Monjalon wrote: > Don't you think adding a bug tracker would artificially split discussions > between mailing list threads and bug tracker entries? It is difficult to track the workflow around bugs without some kind of bug-friendly workflow tool. I.e. Suspected Confirmed Triaged Patched Tested Committed (in master / development branch) Released (in version X.Y.Z) etc. Importantly, Suspected, Confirmed, and Triaged all happen before anything appears in a patch manager tool if I'm not mistaken, and Committed and Released are also not likely present there. So a patch tool only covers 2/7 steps by itself. There are a number of bug tools which have email integration, Bugzilla or Debian BTS. The Debian BTS is especially email friendly, since Debian is a big email community. Since DPDK is for hackers I think it makes more sense to be email friendly than web-friendly like Github or JIRA. Matthew.