From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [ANN] ditz 0.1 Released
Date: Wed, 02 Apr 2008 14:17:38 -0700 [thread overview]
Message-ID: <1207171051-sup-272@south> (raw)
Why not spam you guys too? The plan is to start using this to track Sup
bugs & feature requests a little more systematically than has been done
so far.
ditz version 0.1 has been released!
* <http://ditz.rubyforge.org>
Ditz is a simple, light-weight distributed issue tracker designed to work with
distributed version control systems like darcs and git. Ditz maintains an issue
database file on disk, written in a line-based and human-editable format. This
file is kept under version control, alongside project code. Changes in issue
state is handled by version control like code change: included as part of a
commit, merged with changes from other developers, conflict-resolved in the
standard manner, etc.
Ditz provides a simple, console-based interface for creating and updating the
issue database file, and some rudimentary HTML generation capabilities for
producing world-readable status pages. It offers no central public method of
bug submission.
Synopsis:
# set up project. creates the bugs.yaml file.
1. ditz init
2. ditz add-release
# add an issue
3. ditz add
# where am i?
4. ditz status
5. ditz todo
# do work
6. write code
7. ditz close <issue-id>
8. commit
9. goto 3
# finished!
10. ditz release <release-name>
Changes:
## 0.1 / 2008-04-02
* Initial release!
* <http://ditz.rubyforge.org>
--
William <wmorgan-sup at masanjin.net>
reply other threads:[~2008-04-02 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1207171051-sup-272@south \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox