Le 03/03/12 02:11, John Du Hart a écrit :
I'm currently investigating alternative bug
tracker and project management
software for MediaWiki. To do that I'll be installing some different
software on the Labs and importing existing bugs for evaluation by the
development team and users.
Hello John,
I beg you to first establish a list of requirements and features we are
looking after. You do not want to invest any time installing a software
we could dismiss right away just by looking at its specs (see at the
bottom of this mail for examples).
Let me ask you a question, why do you feel we should move to another bug
tracker?
Do you think that Bugzilla is missing features we could use?
For example, maybe some bug tracker also assist in planning release
management. I know Mantis has a nice interface for that.
Is that because other tools have a nicer interface? We could probably
enhance the Bugzilla one.
I am not a huge fan of Bugzilla. It is certainly lagging in terms of
neat features lack reporting and ease of navigation between components.
But so far, Bugzilla seems to fit our needs nicely.
As for testing there is probably no point in loading our existing bugs
since close to nobody, beside hexmode, know our bugs well enough to take
advantage of it. Instead we can use some demo accounts or just install
a version for sandboxing purposes. Both way would be easier than
investing time in migrating bugs to some other tracker.
If you want some bugs, you can try out Bugzilla JSON interface which is
used to generate the release reports. Entry point is:
https://bugzilla.wikimedia.org/jsonrpc.cgi
Guillaume wrote a blog post about bug tracker, you might want to have a
look at it:
http://www.gpaumier.org/blog/520_scaling-up-software-development-for-wikime…
Find below my comments about the proposed softwares:
The following software is planned for test:
-
JIRA<http://www.atlassian.com/software/jira/overview>
+ Greenhopper + Bonfire
I guess it was installed on Toolserver just because it was written in
Java, a language that River Tarnell like.
Anyway, I would dismiss it just because that is a proprietary software.
Proprietary software as well.
The later being a fork of the former. Both are written in ruby which, as
far as I know, our operation team do not want to hear about on our
production cluster.
Demo:
http://www.opensourcecms.com/demo/1/259/The+Bug+Genie
If you have any suggestions for this list I'd be
glad to hear it.
Have a look at mantis
http://www.mantisbt.org/ :-) I like it a lot.
--
Antoine "hashar" Musso