pcp
[Top] [All Lists]

Re: [pcp] Bug/Issue tracker

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] Bug/Issue tracker
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 22 Apr 2015 00:23:15 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5536B493.5070208@xxxxxxxxxxxxxxxx>
References: <20150420174712.GH18943@xxxxxxxxxxxxxxx> <5536B493.5070208@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: I38+9z+Ok/cq7gWG/A0niNxI+Wg0iQ==
Thread-topic: Bug/Issue tracker
Hi Ken,

----- Original Message -----
> [...]
> My thoughts on this are ...
> 
> - I don't like multiple issue tracking repositories

+1

> - the current github spate seems to have been triggered by the Netflix
> Vector announcement, and I wonder if it will continue

No doubt that's the trigger, but the point is people have (100%) chosen
to report their pcp problems via either github or email, noone has used
bugzilla at all so far (aaaand... no doubt someone now will).

> - since many of the github "issues" seem to be really, in the "this does
> not work for me" or "this does not seem right" categories, I would
> suggest we actively engage with the github posters to answer their
> questions and (a) close the issue, or (b) when it raises a real problem
> move the issue to one of the bugzilla repositories and then close the
> issue on github

Hmm, I agree with (a) but the (b) above seems like double handling to me
with no added value.

> This would turn the github "issues" into more of a forum, and leave the
> hard core issue tracking as it is today ... split in TWO places, sigh.

Well the opportunity if before us right now to resolve this since Michele
is offering to do the work of consolidating the two - is there any reason
why "hard core" issues couldn't be tracked in github instead?

cheers.

--
Nathan

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