My company uses:

Mantis + SVN + svk (for branching)

Mantis has a really nice plugin for commits that catches "bug XXXX"
and appends the commit to the bug status.

- jake

On Sun, Dec 21, 2008 at 2:33 PM, Robert Castley
<robert.cast...@macro4.com> wrote:
> Hi,
>
> Just curious here.  I/we currently use  Bugzilla & CVS, no formal wiki but I
> do have a MediaWiki used for somethings.
>
> I am looking for a solution that fits all, so the obvious choices are 'Trac'
> like.
>
> My problem is that I need a solution that will support multiple projects.
> (Trac doesn't score well in this area.)
>
> Bugzilla is used by multiple PHP, Java & C/C++ products.  CVS is used only
> by PHP developers the 'others' use VSS.
> MediaWiki is used for 'sparse' documentation.
>
>
> My gripes with the current setup:
>
> Bugzilla - v. slow and ugly but it fitted the bill at the time.
> CVS - I like, no love, CVS but I know that there are better solutions out
> there but am concerned about migration etc.
> MediaWiki - Probably too much of an overkill for what we need and it is not
> that easy to configured, extend etc.
>
> I now that the ZF team uses JIRA, Confluence etc but I have a budget of
> £0/$0 :-) and don't qualify for the OS licenses.
>
> So ... I would be interested on the views of others of a 'one hat fits all'
> solution that can handle multiple projects.
> The solution needs to offer Issues/Bug tracking and Wiki at a minimum.
> Integration with SCM not important but
> if it does it great.
>
> I would prefer a PHP based solution but happy to consider others i.e. Ruby,
> Perl, Java etc.
>
> - Robert
>
>
> ________________________________________________________________________
> This email has been scanned for all known viruses by the MessageLabs Email
> Security Service and the Macro 4 plc internal virus protection system.
> ________________________________________________________________________
>

Reply via email to