Bug tracking

Kaleb S. KEITHLEY kkeithle at redhat.com
Tue Jun 21 13:45:34 UTC 2011


On 06/08/2011 10:14 AM, Jeff Darcy wrote:
> It's time to start tracking bugs (including feature requests and
> development tasks) in a more transparent and history-friendly way. As I
> see it, we have three options:
>
> * Use bugzilla.redhat.com - probably not the right answer for now (maybe
>    when it's an actual Red Hat supported product)
>
> * Use TRAC at fedorahosted - better integration with the git tree that's
>    already there, also serves as a project website, requires only an
>    infrastructure request . . . but it's TRAC
>
> * Use a private bug tracker - I've already set up an instance of Mantis
>    at http://cloudfs.org/bugs and found it useful to track issues during
>    development of the socket code. I'm not tied to Mantis; it was just
>    easier for me to install on my shared web host than CGI-based
>    alternatives such as bugzilla or TRAC would have been.
>
> What do others think?

I went off in search of TRAC. The only things I have found in the 
f'project/f'hosted wiki seems to suggest that TRAC is how issues with 
fedora _infrastructure_ are tracked.

Furthermore the only thing I can find WRT tracking bugs in fedora 
features is the strong suggestion to use bugzilla.redhat.com. 
Bugzilla.redhat.com is publicly accessible. Using it now, versus 
migrating to it later means not having to do the migration. Presuming 
that there will be enough (valuable) content in the defect reports to 
warrant migrating them.

Have I missed something?



More information about the cloudfs-devel mailing list