Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Aug 2011 12:29:58 -0700 (PDT)
From:      "Pedro F. Giffuni" <giffunip@tutopia.com>
To:        Eitan Adler <lists@eitanadler.com>
Cc:        freebsd-arch@freebsd.org
Subject:   Re: How about finally replacing GNATS? (was Re: FreeBSD problems and preliminary ways to solve)
Message-ID:  <1314473398.47547.YahooMailClassic@web113509.mail.gq1.yahoo.com>
In-Reply-To: <CAF6rxgnbXVHjvL%2BNVCTSUjg25KOpg7amf4Xz_KHDStF1kwYYHQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi;

--- On Sat, 8/27/11, Eitan Adler <lists@eitanadler.com> wrote:

...

I agree it's difficult to determine exactly which tool to
use.

> 
> With every tool change comes a workflow change and we need
> to be able to deal with that. As a member of the bugbusting
> team one of the most useful features for me has been the
> ability to use shell scripts to change bug states. As a
> port maintainer one of the most useful features has been
> the ability to use send-pr from the command line
> _without registration_. 

I do think port maintainers should have some form of ID in
the bug reporting system. Casual users probably won't send
a PR anyways but instead will contact the port maintainer
first.

...

(I snipped without mercy a lot of good stuff here)
> 
> In order to achieve that goal I am working on two things:
> a) A wiki page which we could use to describe the features
> we want *in order of priority* and b) A Google form with
> a list of features and related issues to act as a survey.
> The former is quite empty at the moment.
> The latter will be announced (hopefully) shortly
>

Surveys are good but you have to tie it to the specific
alternatives, otherwise you will reach the already known
answer that a perfect bug reporting system doesn't exist.

Pedro. 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1314473398.47547.YahooMailClassic>