pcp
[Top] [All Lists]

Bug/Issue tracker

To: pcp developers <pcp@xxxxxxxxxxx>
Subject: Bug/Issue tracker
From: Michele Baldessari <michele@xxxxxxxxxx>
Date: Mon, 20 Apr 2015 19:47:12 +0200
Delivered-to: pcp@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=acksyn.org; h= user-agent:content-disposition:content-type:content-type :mime-version:message-id:subject:subject:from:from:date:date :received:received; s=2010; t=1429552033; bh=WRy4785NKIOOeODaNN4 rFtVJBhgfrBa4NyYdaHed+I8=; b=gL7TZB8haTctoJtcp+X75G70cjO9lFROkh7 Gasl6eWbCD4ozRmaQWGn+QzK/DosMtnfbVf75k6Jr5sBQu2dmPRFngb3Hn9Y2Tvr GpwlnBcIs/YEwC7yOg0i3l7H1fouVXkmWbxgk6Wz3EkRbhi/IMiV1xirSbav3+L+ 19qBy2MI=
User-agent: Mutt/1.5.23.1-rc1 (2014-03-12)
Hi all,

we currently have issues/enhancements filed in three different places:
1. SGI Bugzilla (92 bugs open atm)
2. Github Issue Tracker (9 issues open atm)
3. Red Hat Bugzilla (mainly for issues with packaging in RHEL/Fedora or
   any Red Hat specific process - I am excluding this one from the
   proposal below)

Since I'd like to add a simple "Bug Reporting" webpage to pcp.io, I think it
makes sense to consolidate 1. and 2. into a single source.

Here are the pro/contra I can think of for choosing the main bug DB.
- Github
Pro: 
  integrates well with existing git workflow
  massive userbase so no need to create an account just to file a bug
  much more user friendly to file an issue
Contra:
  some migration work
  issue tracking is a bit more simplistic than bugzilla

- SGI Bugzilla
Pro:
  most bugs are already there
Contra:
  cumbersome to use and to file new issues
  requires an account which users are unlikely to have
  
I think that to make things easier for users it makes more sense to
switch to github fully for issue tracking purposes. If there is rough
consensus on this, I'll work on some test scripts to migrate all bugs
w/comments and attachments. If there is vast disagreement we can also
move everything to SGI's bugzilla instance.

I think in the long term it might be a bit easier to do some
roadmap/release planning in the open by using a single source of issues.

Thoughts on this?

cheers,
Michele
-- 
Michele Baldessari            <michele@xxxxxxxxxx>
C2A5 9DA3 9961 4FFB E01B  D0BC DDD4 DCCB 7515 5C6D

<Prev in Thread] Current Thread [Next in Thread>