.\"                                      Hey, EMACS: -*- nroff -*-
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH DITRACK 1 "April 2007"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
.\" .nh        disable hyphenation
.\" .hy        enable hyphenation
.\" .ad l      left justify
.\" .ad b      justify to both left and right margins
.\" .nf        disable filling
.\" .fi        enable filling
.\" .br        insert line break
.\" .sp <n>    insert n+1 empty lines
.\" for manpage-specific macros, see man(7)
.SH NAME
dt \- DITrack command line client tool
.SH SYNOPSIS
\fBdt\fP \fIcommand\fP [\fIoptions\fP] [\fIargs\fP]
.br
\fBdt-createdb\fP \fIrepository-url\fP \fIissue-db-dir\fP \fIlocal-wc\fP
.br
\fBdt-upgrade-0.7-db\fP \fIissue-db-dir\fP
.SH OVERVIEW
DITrack is a free, open source, lightweight, distributed issue (bug,
defect, ticket) tracking system using a Subversion repository instead
of a backend database. It is written in Python and runs in UNIX
environment (*BSD, Linux, MacOS X).

The project is inspired by the idea of Subissue issue tracking system.

However, while Subissue aims in merely replacing the traditional
database storage with Subversion repository, DITrack is a major
rethought of the issue tracking system paradigm. The main difference
is that instead of sticking to the centralized model (one database,
one web interface, one mail integration machinery), DITrack treats
underlying Subversion storage as a versioned distributed file system
which enables benefits of truly distributed operation mode. 

For more information about the DITrack project, visit
http://www.ditrack.org.

Documentation for DITrack and its tools, including detailed usage
explanations of the \fBdt\fP and \fBdt-createdb\fP programs,
can be found at /usr/share/doc/ditrack/html/index.html.

Run `dt help' to access the built-in tool documentation.

Automatic upgrade is possible for databases created by DITrack 0.7. If
you are upgrading from previous version of DITrack, use the upgrage
utility from DITrack 0.7 first.

To upgrade a database run the \fBdt-upgrade-0.7-db\fP script, passing
the database path as the argument, like:

\fBdt-upgrade-0.7-db\fP \fI/home/user/ditrack-database\fP

The upgrade procedure merely modifies the working copy (nothing gets
committed to the repository). So, when done, you should commit the
changes manually.