fix some naming issues
This commit is contained in:
parent
0cdf94e790
commit
778a2c3f5b
22 changed files with 0 additions and 0 deletions
21
content/post/cli-bugissuetask-tracking-system.md
Normal file
21
content/post/cli-bugissuetask-tracking-system.md
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
+++
|
||||
date = "2007-03-05T17:03:00-07:00"
|
||||
title = "cli bug/issue/task tracking system?"
|
||||
categories = ["software"]
|
||||
tags = ["cli"]
|
||||
+++
|
||||
|
||||
cli bug/issue/task tracking system?
|
||||
===================================
|
||||
|
||||
Fresh from freshmeat:
|
||||
|
||||
https://www.ditrack.org/
|
||||
|
||||
What is DITrack?
|
||||
|
||||
DITrack is a free, open source, lightweight, distributed issue (bug, defect, ticket) tracking system using a [Subversion](https://subversion.tigris.org/) 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](https://subissue.tigris.org/) 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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue