[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[RFC] which bug tracker to use?

From: Greg Stein <gstein_at_gmail.com>
Date: Mon, 9 Nov 2009 10:10:06 -0500

Hi all,

Now that we're in the Incubator and on our way to becoming an Apache
project, one of the items that we need to select is which bug tracker
to use.

I'll preface this with: the ASF does not *mandate* that we use its
facilities for bug tracking. It only wants source control and the
original distribution point to be on ASF hardware. I'm not necessarily
advocating that we keep a separate tracker (user confusion), but it is
possible. Weigh the pros/cons in your mind.

The ASF provides two bug trackers:

1) Jira at http://issues.apache.org/jira/

2) Bugzilla at http://issues.apache.org/bugzilla/

In our discussion with the ASF Infrastructure Team, they have no
preference on which we choose. Both are equally supported.

For completeness:

3) Stick to Issuezilla on tigris.org

4) Use the issue tracker on Google Code in <some> appropriate project.
[this is my favorite tracker!]

5) Set up our own tracker on ASF hardware (eg. Trac). [I do not
recommend this; our project would have to maintain it; ASF Infra only
maintains Jira/Bugzilla]

For all options, other than (3), we will get a data dump of Issuezilla
from tigris.org (via XML export, or SQL datadump) and coax that into
the new tracker. I believe we can keep the same issue numbers in all

Lastly: note that since we are not required to use ASF hardware, the
move to a new issue tracker is not a requirement for Incubator
graduation. While I hope to see us graduate in about 7 weeks, we can
take several months to get the issue tracker migration Done Right.

Please provide your thoughts and comments. If there is no clear
direction, then we'll run a poll on the topic.


Received on 2009-11-09 16:11:05 CET

This is an archived mail posted to the Subversion Dev mailing list.