|
1
|
1 Welcome to swallowtail!
|
|
|
2
|
|
|
3 swallowtail is a bugtracking system meant to serve as a migration path
|
|
|
4 for large GNATS installations. It was designed with the following
|
|
|
5 assumptions:
|
|
|
6
|
|
|
7 - the database and its access tools are to be installed and
|
|
|
8 operating on a project server somewhere such that project
|
|
|
9 members have shell access and outsiders have web access;
|
|
|
10 - that project members do not need to be baby-sat;
|
|
|
11 - there is a large pre-existing bug database to be imported;
|
|
|
12 - the pre-existing database contains fields reflecting the
|
|
|
13 hardcoded GNATS data semantics;
|
|
|
14 - hand-editing any substantial fraction of the database is
|
|
|
15 impossible;
|
|
|
16 - incoming bug reports are submitted from a deployed base of
|
|
|
17 legacy GNATS send-pr scripts that can be superseded in the
|
|
|
18 wild only gradually;
|
|
|
19 - that there are relatively few preexisting database access
|
|
|
20 tools, such that replacing them all is readily feasible;
|
|
|
21 - enabling sql-based access to support new and custom tools is
|
|
|
22 more useful and of more interest than providing canned user
|
|
|
23 interface features;
|
|
|
24 - the database is too large for manual search, but not
|
|
|
25 necessarily too large for manual or manually-assisted
|
|
|
26 indexing;
|
|
|
27 - that multiple types of semantic indexing will be required,
|
|
|
28 and that tools should not have to treat each new index
|
|
|
29 scheme as a fresh special case.
|
|
|
30
|
|
|
31 It uses PostgreSQL for data storage. Other required software is as
|
|
|
32 follows:
|
|
|
33
|
|
|
34 [TBD]
|
|
|
35
|
