Re: [Audacity-devel] Does Bugzilla still have a case?
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale A. <ga...@au...> - 2009-12-06 10:44:28
|
| From James Crook <cr...@in...> | Fri, 04 Dec 2009 14:59:54 +0000 This was in "Release often; 1st Jan/1st Feb". > I'd like a decision from Gale on whether we should be on *Bugzilla* by > the 1st Jan. If we are going to move by then I think we should aim to > have the move done by 20th Dec, as otherwise it will be too disruptive > around the release time. I'm OK with it continuing to be undecided > whether Bugzilla is right for us for quite a long time, say even until > around May 2010. If it is still undecided then, then 'by fiat' Bugzilla > is not right for us, and in my view it is worth diverting some developer > energy, probably mine, to writing a better bug tracker that combines > advantages of wiki and normal bugtrackers. I still need some quality time using Bugzilla to be "sure", though it seems most of its problems are tweakable. The potential problem of the comments not being open to editing/pruning is hard to assess until it's used in anger, but I guess other Bugzilla users manage somehow? I'm a bit concerned this might cause us to start splitting/restarting bugs more than we might need to. I'd like to be able to decide in principle by mid January, but equally we don't want to put lots of effort into Bugzilla if the prospect of something better is realistic. I don't have a very clear picture of how a Wiki system of one bug per page (after the scatter-gather has been implemented) would work, or how well it would cope with a large quantity of bugs if we maintain the "assiduous" approach to bug tracking. Large numbers of bugs might seem to imply starting from a database solution, not from a text solution. Can Bugzilla be hacked to produce summaries/category lists and so on? And do you think the ideal bug tracker is sufficiently better than pure database that it justifies a lot of developer resources, rather than some other development for the app itself? I don't know the answers to those questions (or the resources needed to produce something better), so I'm trying to get a feel for it. Thanks Gale |