bugtracker
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
bugtracker [2008/07/03 13:39] klette added conclusion |
bugtracker [2008/07/03 13:45] klette |
||
|---|---|---|---|
| Line 161: | Line 161: | ||
| Not hosting it ourselfs provides to major benefits. First and most important is the fact that we dont have to maintain or do anything | Not hosting it ourselfs provides to major benefits. First and most important is the fact that we dont have to maintain or do anything | ||
| regarding the administration, or development on the codebase it self, nor the hardware its running on. Secondly it may give us some publicity and further help us in our goal in becoming more open in our development. | regarding the administration, or development on the codebase it self, nor the hardware its running on. Secondly it may give us some publicity and further help us in our goal in becoming more open in our development. | ||
| + | As another factor in this is the both ways support for emails on launchpad - if we want this in trac, we are going to have to make it ourselfs, taking even more time away from solving the tasks that we are supposed to be solving. | ||
| + | |||
| + | Because of these reasons, I suggest as of today that we switch from sourceforge.net to launchpad | ||
| + | |||
| + | ===== Bugtrackers not tested ===== | ||
| + | * Google code - Main feature is code-hosting. Bugtracker is not really there yet. | ||
| + | * Flyspray - Has serious performance issues, and code quality is known to be under par. | ||
| + | * Request Tracker - Not really a tool that helps opening the development. Its a behemoth not fitting our needs | ||
| - | I suggest as of today that we switch from sourceforge.net to launchpad | ||
bugtracker.txt ยท Last modified: 2008/07/04 20:09 by klette
Page Tools
