From: Bill Lear <rael@zopyra.com>
To: Rakotomandimby Mihamina <mihamina@gulfsat.mg>
Cc: git@vger.kernel.org
Subject: Re: choosing an issue tracker
Date: Wed, 2 Dec 2009 05:54:24 -0600 [thread overview]
Message-ID: <19222.21872.425947.273352@lisa.zopyra.com> (raw)
In-Reply-To: <4B16331A.3060606@gulfsat.mg>
On Wednesday, December 2, 2009 at 12:27:54 (+0300) Rakotomandimby Mihamina writes:
>Hi all,
>
>For a while, I used SVN and Trac.
>They have a satisfying mutual integration.
>
>I am looking for our new issue tracker, and would like to be advised.
>
>Our context:
>- developpers using git, developping
> - web based applications (PHP, Python, OCaml,...)
> - Unix-like system maintainance scripts (SHELL, Perl,...)
>- a QA guy that makes functional tests only on the web applications
> and reports bugs and potential improvements. He does not use git.
>- multiple projects
>
>What we look for:
>something like the (Trac, SVN) but with git as SCM.
>
>What issue tracker would you recommend?
You might be interested in Jira, which I have tied to git with my
open-source niftyism:
http://github.com/rael/git-jira
Bill
prev parent reply other threads:[~2009-12-02 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 9:27 choosing an issue tracker Rakotomandimby Mihamina
2009-12-02 9:40 ` Matthieu Moy
2009-12-02 11:54 ` Bill Lear [this message]
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=19222.21872.425947.273352@lisa.zopyra.com \
--to=rael@zopyra.com \
--cc=git@vger.kernel.org \
--cc=mihamina@gulfsat.mg \
/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