Since we are changing our entire developing structure and using a lot of modern things I am not sure how we should treat our bugtracker. Actually I am quite happy with the one we are using right now. I remember that we installed the bugtracker when we first released our beta version of Metalcon. But I had the feeling that the bugtracker is already a great tool to support todos while creating software.
Do you think we should use the bugtracker right away while developing metalcon or do we just communicate over the wiki?
Since the developement of the new metalcon version is going to be much more decentralized I would love to integrate the bugtracker as one of our core communication channels. It really helps to set priorities of tasks and stay more focussed and assign tasks to specific persons on the team.
by the way what happened to the old bugtracker? bugs.metalcon.de directs to metalcon.de
I would definitely go for a bug tracker again! Actually I don’t think that I want to install mantis again. It is quite nice and slim but I would love to use one of the eclipse-plugins which is not possible with mantis (as far as I know). I know of a nice plugin based on bugzilla where you can even save your current eclipse-view. Meaning if you click on a bug eclipse opens the windows you have had opened while you’ve committed the last version of the bug.
What about google code? Don’t they have an included bugtracker too? I can have a look on that later…
Oh I love the idea of having a bug tracker integrated to eclipse! That would really be very convenient. i trust you to find a good solution but keep in mind that there has to be a web interface for our users.