|
tools useful for A-A-P
The intention for A-A-P is to use existing tools as much as possible. To find
out which tools can be used this overview has been compiled.
Some tools cannot be used directly, but function as an example or can be
invoked by A-A-P (e.g., commercial tools and programs which are not portable).
Unless noted otherwise, tools are open-source.
If you find a tool that would be useful for A-A-P but is not listed here, or
when information is incorrect, send a message to
Bram AT a-a-p.org.
Note: this list is not intended to be complete. Information that is
irrelevant for A-A-P is omitted.
Script languages
Build
Install
Issue Tracking
Version control
Browse
IDEs
Various
Issue tracking
This includes bug tracking. Another term is change request handling. This
not only is for handling bug reports, but also request for new features and
planning future work. Can also be seen as a todo list.
Currently the intention for A-A-P is to interface with existing systems, and
recommend one of them for new projects.
Overview (random order):
- bugzilla
-
Bug tracker written in Perl. Uses mySQL.
Works fine for most things, but does have a few disadvantages.
This is what most other open-source bug trackers compare against.
Widely used, should be supported by A-A-P.
- IssueZilla
-
Web based bug tracker. Open source version of bugzilla.
But it's done by Collabnet, which is commercial?
Used by open-source projects, should be supported by A-A-P.
- GNATS
-
GNU bug tracker.
Supports command-line use, e-mail, web interface, etc.
Widely used, should be supported by A-A-P.
- Jitterbug
-
Web based bug tracker.
Was originally made for Samba.
Implemented in C, requires a web server.
Includes an SMTP mail client.
Does not use a database, stores messages as separate files.
Looks a bit primiteve but it's used. Should be supported by A-A-P.
- SourceForge
-
Web based bug tracker.
It's unclear on what this is based.
Used by many open-source projects, should be supported by A-A-P.
- Roundup
-
Issue tracker, used from command-line, web and mail.
Supports a web and e-mail interface.
Implemented in Python.
Still new (version 0.5.0) but well documented.
Sounds good, but not generally used yet.
- Scarab
-
Implemented with Java Servlet technology.
Can also be used integrated, e.g., with CollabNet's SourceCast.
Can import and export XML for migration from/to other systems.
Still new, version 1 is in beta testing.
Sounds good, but not generally used yet.
- mantisbt
-
Bug tracker based on PHP. In beta testing.
Sounds good, but not generally used yet.
- phpbt
-
Bug tracker in PHP, supposed to be a replacement for BugZilla.
Supports multiple projects.
Still in beta testing.
Sounds good, but not generally used yet.
- bugbase
-
Bug tracker in Java.
Supports multiple projects.
Supports two databases: mySQL and Hypersonic.
Still in beta testing.
Sounds good, but not generally used yet.
- workbench
-
Bug tracker in PHP and using mySQL.
Still in beta testing.
Sounds good, but not generally used yet.
- BugIn
-
Bug tracker in PHP and mySQL.
Still in early beta testing.
Not generally used yet.
- bugtracker
-
Issue tracker in Java.
Still in early beta testing.
Not generally used yet.
- NITS
-
Issue tracker. Commercial.
Is anyone using this?
- TrackStudio
-
TrackStudio is a hierarchical issue tracking and bug tracking system,
created specifically for software development companies.
Commercial. There is a free trial to download.
- sBugs
-
Bug tracker written in JSP and Java, and currently uses PostgreSQL for
storage.
Still in alpha testing.
Another page with an issue tracker overview:
ZopeIssueTrackers.
|
|